From: Derrick Stolee <stolee@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
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:47:32 -0400 [thread overview]
Message-ID: <c3d41848-f15d-99af-22fb-d6de2859bd93@gmail.com> (raw)
In-Reply-To: <87a7uwxai4.fsf@evledraar.gmail.com>
On 3/25/2018 2:42 PM, Ævar Arnfjörð Bjarmason wrote:
> On Sun, Mar 25 2018, Derrick Stolee wrote:
>
>> 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.
> I haven't deployed any actual use of it at a wider scale, but I've done
> some ad-hoc benchmarking with our internal version which has your
> patches, and the results are very promising so far on the isolated test
> cases where it helps (that you know about, e.g. rev-list --all).
>
> So sorry, I don't have any meaningful testing of this, I just wanted an
> easy way to ad-hoc test it & make sure it doesn't break other stuff for
> now.
>
> I also threw out most of the manual git maintenance stuff we had and
> just rely on gc --auto now, so as soon as you have something to
> integrate with that, along with those perf changes Peff suggested I'm
> much more likely to play with it in some real way.
Thanks. Integration with 'gc --auto' is a high priority for me after the
patch lands.
The version on GitHub [1] is slightly ahead of v6 as I wait to reroll on
v2.17.0. It includes Peff's improvements to inspecting pack-indexes [2].
[1] https://github.com/derrickstolee/git/pull/2
[2]
https://github.com/derrickstolee/git/pull/2/commits/cb86817ee5c5127b32c93a22ef130f0db6207970
prev parent reply other threads:[~2018-03-25 18:47 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
2018-03-25 18:42 ` Ævar Arnfjörð Bjarmason
2018-03-25 18:47 ` Derrick Stolee [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=c3d41848-f15d-99af-22fb-d6de2859bd93@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.
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).