threads / discuss / 51849

Git versioning policy - PatchMyPC compatibility on Windows

Subject: Git versioning policy - PatchMyPC compatibility on Windows

## tl;dr

3 messages between Sep 14, 2019 and Sep 14, 2019.

replies: 2people: 3as markdown or json

Audric GUERIN· Sep 14, 2019, 12:49 UTC · lore
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
brian m. carlson· Sep 14, 2019, 19:38 UTC · re: Audric GUERIN · lore

Re: Git versioning policy - PatchMyPC compatibility on Windows

On 2019-09-14 at 12:49:40, Audric GUERIN wrote:
Show 15 quoted lines
> 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.

Show 6 quoted lines
> 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
Philip Oakley· Sep 14, 2019, 20:39 UTC · re: brian m. carlson · lore

Re: Git versioning policy - PatchMyPC compatibility on Windows

On 14/09/2019 20:38, brian m. carlson wrote:
Show 34 quoted lines
> 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

← back to recent threads