git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org, Takuto Ikuta <tikuta@chromium.org>,
	Duy Nguyen <pclouds@gmail.com>
Subject: Re: [ANNOUNCE] Git v2.17.0-rc1
Date: Sun, 25 Mar 2018 14:19:19 -0400	[thread overview]
Message-ID: <e2d0a2e2-44a1-9aa6-9c52-e341b44c18f4@gmail.com> (raw)
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

  reply	other threads:[~2018-03-25 18:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21 19:50 [ANNOUNCE] Git v2.17.0-rc1 Junio C Hamano
2018-03-23 17:47 ` Johannes Schindelin
2018-03-24  3:02   ` Bryan Turner
2018-03-26 16:37     ` Johannes Schindelin
2018-03-23 17:59 ` Ævar Arnfjörð Bjarmason
2018-03-25 18:19   ` Derrick Stolee [this message]
2018-03-25 18:42     ` Ævar Arnfjörð Bjarmason
2018-03-25 18:47       ` Derrick Stolee

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=e2d0a2e2-44a1-9aa6-9c52-e341b44c18f4@gmail.com \
    --to=stolee@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@gmail.com \
    --cc=tikuta@chromium.org \
    /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).