From: Philip Oakley <philipoakley@iee.email>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Audric GUERIN <audric.guerin@gmail.com>,
git@vger.kernel.org
Subject: Re: Git versioning policy - PatchMyPC compatibility on Windows
Date: Sat, 14 Sep 2019 21:39:37 +0100 [thread overview]
Message-ID: <10d0e87d-1ba8-bb82-bf9d-72a468c16bb0@iee.email> (raw)
In-Reply-To: <20190914193825.GS11334@genre.crustytoothpaste.net>
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
prev parent reply other threads:[~2019-09-14 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-14 12:49 Git versioning policy - PatchMyPC compatibility on Windows Audric GUERIN
2019-09-14 19:38 ` brian m. carlson
2019-09-14 20:39 ` Philip Oakley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10d0e87d-1ba8-bb82-bf9d-72a468c16bb0@iee.email \
--to=philipoakley@iee.email \
--cc=audric.guerin@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).