Re: AW: 4.6.3 tag in git repository

[Daniel J S. <dan...@ie...>]

On 11/13/2017 05:16 AM, Bastian Märkisch wrote:
>> -----Ursprüngliche Nachricht-----
>> Von: Daniel J Sebald [mailto:dan...@ie...]
> (snip)
>> That is, delete tag [4.6.3] and add a new tag [4.6.3] on the new branch
>> (stub) which has the patch.  This puts version tagged [4.6.3] in line with
> cvs-
>> repository and the tarball.  Add a new tag [4.6.3-Windows] to signify that
> is the
>> release that Bastian has published for 4.6.3 that includes everything in
> the
>> 4.6.3 tagged version plus the mods to four Windows-related files.
>>
>> Dan
> 
> Not sure about the necessity for a Windows tag.  The missing change only
> affects the installer, not gnuplot itself, in that it modifies the numbers
> and filename there to reflect the patchlevel.
> 
>    Bastian

Right.  These small touchups just before release that aren't in the 
repository can be recreated by branching a stub of the labeled release 
and expanding the tarball if one wants to do so.

This archive

https://sourceforge.net/projects/gnuplot/files/gnuplot/4.6.3/gp463-win32.zip/download

appears to match what I suggested be [4.6.3-Windows]; that's why I 
suggested adding the tag, i.e., resolve confusion.

Dan

PS: I forgot the comparison script (attached), if you want to run it there.