From: Philip Oakley <philipoakley@iee.email>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>
Cc: git-for-windows@googlegroups.com, git@vger.kernel.org,
git-packagers@googlegroups.com
Subject: Re: [git-for-windows] Git for Windows v2.24.0-rc0, was Re: [ANNOUNCE] Git v2.24.0-rc0
Date: Tue, 22 Oct 2019 15:50:28 +0100 [thread overview]
Message-ID: <74f50326-e613-8545-2c69-65cd29dd3cfb@iee.email> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1910220004190.46@tvgsbejvaqbjf.bet>
Hi Dscho,
Install went Ok.
Did a quick test on the config locations and `git config -l
-show-origin` has 'lost' the ProgramData location as planned.
The minor pedant did notice that the new location is listed slightly
differently from the release notes.
`file:C:/Program Files/Git/mingw64/../etc/gitconfig` --system,
while the release notes simplify the path to C:/Program
Files/Git/etc/gitconfig
Dunno if that's worth a minor fix to the release notes to clarify for
the broader Windows community. Maybe others can comment if they think
it's even worth it.
Philip
On 21/10/2019 23:05, Johannes Schindelin wrote:
> Team,
>
> a couple of days later than I wanted, but at least it is now here:
> https://github.com/git-for-windows/git/releases/tag/v2.24.0-rc0.windows.1
>
> Please test...
>
> Thank you,
> Johannes
>
>
next prev parent reply other threads:[~2019-10-22 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 6:29 [ANNOUNCE] Git v2.24.0-rc0 Junio C Hamano
2019-10-21 20:48 ` Derrick Stolee
2019-10-21 23:04 ` Elijah Newren
2019-10-22 6:42 ` Jeff King
2019-10-21 22:05 ` Git for Windows v2.24.0-rc0, was " Johannes Schindelin
2019-10-22 14:50 ` Philip Oakley [this message]
2019-10-24 23:08 ` [git-for-windows] " Johannes Schindelin
2019-10-24 23:34 ` Jeff King
2019-10-25 8:18 ` Johannes Schindelin
2019-10-25 16:58 ` Jeff King
2019-10-24 18:24 ` Bryan Turner
2019-10-24 22:52 ` Johannes Schindelin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=74f50326-e613-8545-2c69-65cd29dd3cfb@iee.email \
--to=philipoakley@iee.email \
--cc=Johannes.Schindelin@gmx.de \
--cc=git-for-windows@googlegroups.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
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 NNTP newsgroup(s).