From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Takuto Ikuta <tikuta@chromium.org>,
Duy Nguyen <pclouds@gmail.com>, Derrick Stolee <stolee@gmail.com>
Subject: Re: [ANNOUNCE] Git v2.17.0-rc1
Date: Fri, 23 Mar 2018 18:59:07 +0100 [thread overview]
Message-ID: <87k1u2y8pg.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqtvt9nr7p.fsf@gitster-ct.c.googlers.com>
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
> * Some bugs around "untracked cache" feature have been fixed. This
> will notice corrupt data in the untracked cache left by old and
> buggy code and issue a warning---the index can be fixed by clearing
> the untracked cache from it.
> (merge 0cacebf099 nd/fix-untracked-cache-invalidation later to maint).
> (merge 7bf0be7501 ab/untracked-cache-invalidation-docs later to maint).
FYI over some >10k machines I tested on around 1% had (very) verbose
warnings on "status", which was fixed as a one-off with 'git -c
core.untrackedCache=false status' as the
ab/untracked-cache-invalidation-docs suggest, and it hasn't happened
again since.
next prev parent reply other threads:[~2018-03-23 17:59 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 [this message]
2018-03-25 18:19 ` Derrick Stolee
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=87k1u2y8pg.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=stolee@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.