Git versioning policy - PatchMyPC compatibility on Windows

Git versioning policy - PatchMyPC compatibility on Windows

[Audric GUERIN]

Hi,

I use PatchMyPC to keep all my applications up to date on Windows but 
there is one application that is never properly detected as up to 
date... and it is Git as you guessed.

According to Justin Chalfant, Director of Engineering of PatchMyPC, Git 
version "number" / identifier is not "standard".
https://patchmypc.com/forum/index.php?topic=3032.msg8211#msg8211

PatchMyPC seems not to like that:
Git version identifier = version number + platform specific identifier

command "git version" currently returns:
git version 2.23.0.windows.1

git executables (like git-cmd.exe for instance) displays this "File 
version" on Windows:
2.23.0.1

What are your thoughts? And can you answer to Justin Chalfant on 
PatchMyPC forum?

Regards,

Audric GUERIN

Re: Git versioning policy - PatchMyPC compatibility on Windows

[brian m. carlson]

[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]

On 2019-09-14 at 12:49:40, Audric GUERIN wrote:
> Hi,
> 
> I use PatchMyPC to keep all my applications up to date on Windows but there
> is one application that is never properly detected as up to date... and it
> is Git as you guessed.
> 
> According to Justin Chalfant, Director of Engineering of PatchMyPC, Git
> version "number" / identifier is not "standard".
> https://patchmypc.com/forum/index.php?topic=3032.msg8211#msg8211
> 
> PatchMyPC seems not to like that:
> Git version identifier = version number + platform specific identifier
> 
> command "git version" currently returns:
> git version 2.23.0.windows.1

This is the version number of Git for Windows.  This is a version of Git
developed by the Git for Windows project which contains additional
patches designed to make it work better on Windows than standard Git
(although it will also work on other platforms as well).

The Git project itself doesn't provide binaries; various other people
(such as Linux distros and Git for Windows) provide binaries for their
particular platforms.

> git executables (like git-cmd.exe for instance) displays this "File version"
> on Windows:
> 2.23.0.1
> 
> What are your thoughts? And can you answer to Justin Chalfant on PatchMyPC
> forum?

Since this is a custom build, you'd be better off reaching out to the
Git for Windows project at https://github.com/git-for-windows/git.  They
can help you figure out the best way forward.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]

Re: Git versioning policy - PatchMyPC compatibility on Windows

[Philip Oakley]

On 14/09/2019 20:38, brian m. carlson wrote:
> On 2019-09-14 at 12:49:40, Audric GUERIN wrote:
>> Hi,
>>
>> I use PatchMyPC to keep all my applications up to date on Windows but there
>> is one application that is never properly detected as up to date... and it
>> is Git as you guessed.
>>
>> According to Justin Chalfant, Director of Engineering of PatchMyPC, Git
>> version "number" / identifier is not "standard".
>> https://patchmypc.com/forum/index.php?topic=3032.msg8211#msg8211
>>
>> PatchMyPC seems not to like that:
>> Git version identifier = version number + platform specific identifier
>>
>> command "git version" currently returns:
>> git version 2.23.0.windows.1
> This is the version number of Git for Windows.  This is a version of Git
> developed by the Git for Windows project which contains additional
> patches designed to make it work better on Windows than standard Git
> (although it will also work on other platforms as well).
>
> The Git project itself doesn't provide binaries; various other people
> (such as Linux distros and Git for Windows) provide binaries for their
> particular platforms.
>
>> git executables (like git-cmd.exe for instance) displays this "File version"
>> on Windows:
>> 2.23.0.1
>>
>> What are your thoughts? And can you answer to Justin Chalfant on PatchMyPC
>> forum?
> Since this is a custom build, you'd be better off reaching out to the
> Git for Windows project at https://github.com/git-for-windows/git.  They
> can help you figure out the best way forward.
There is some discussion about the semver approach on 
https://github.com/git-for-windows/git/issues/2223 and how the 
.windows.<n> indicates patches beyond the upstream releases. Semver 
isn't sufficient in these cases.

Philip