From: Derrick Stolee <stolee@gmail.com>
Date: Sun, 25 Mar 2018 18:19:19 GMT
Subject: Re: [ANNOUNCE] Git v2.17.0-rc1
Message-ID: <e2d0a2e2-44a1-9aa6-9c52-e341b44c18f4@gmail.com>
In-Reply-To: <87k1u2y8pg.fsf@evledraar.gmail.com>

On 3/23/2018 1:59 PM, Ævar Arnfjörð Bjarmason wrote:
> On Wed, Mar 21 2018, Junio C. Hamano wrote:
>
>> A release candidate Git v2.17.0-rc1 is now available for testing
>> at the usual places.  It is comprised of 493 non-merge commits
>> since v2.16.0, contributed by 62 people, 19 of which are new faces.
> I have this deployed on some tens of K machines who all use git in one
> way or another (from automated pulls, to users interactively), and rc0
> before that, with a few patches on top from me + Takato + Duy + Derrick
> since rc0 was released (and since today based on top of rc1). No issues
> so far.
>
> The specific in-house version I have is at:
> https://github.com/git/git/compare/v2.17.0-rc1...bookingcom:booking-git-v2018-03-23-1

Thanks for testing the commit-graph feature, Ævar! I'm guessing you have 
some mechanisms to ensure the 'git commit-graph write' command is run on 
these machines and 'core.commitGraph' is set to true in the config? I 
would love to hear how this benefits your org.

Thanks,
-Stolee