From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.15.0-rc0
Date: Thu, 5 Oct 2017 02:09:23 -0400 [thread overview]
Message-ID: <20171005060922.o2wzccm4uqq5o74e@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqq7ewa87fw.fsf@gitster.mtv.corp.google.com>
On Thu, Oct 05, 2017 at 02:55:31PM +0900, Junio C Hamano wrote:
> Git 2.15 Release Notes (draft)
> ==============================
>
> Backward compatibility notes and other notable changes.
>
> * Use of an empty string as a pathspec element that is used for
> 'everything matches' is still warned and Git asks users to use a
> more explicit '.' for that instead. The hope is that existing
> users will not mind this change, and eventually the warning can be
> turned into a hard error, upgrading the deprecation into removal of
> this (mis)feature. That is now scheduled to happen in the upcoming
> release.
I wasn't sure if this "upcoming" meant v2.15 ("the upcoming release that
we're about to tag") or v2.16. Judging from "What's cooking" it's the
latter, but perhaps we should be more explicit. I don't know if you are
hesitant to name it "v2.16" at this point, but maybe:
...in the upcoming release (i.e., the one after v2.15).
would help.
> * Git now avoids blindly falling back to ".git" when the setup
> sequence said we are _not_ in Git repository. A corner case that
> happens to work right now may be broken by a call to die("BUG").
An even more minor nit. This is now BUG(). :)
I don't think it matters for our purposes here, of course. But I did
wonder how long we'd want to carry this warning in the notes. I think it
goes back to v2.13. Of course people sometimes jump several versions
without necessarily reading the interim release notes, so it makes sense
to carry it for a while.
-Peff
next prev parent reply other threads:[~2017-10-05 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 5:55 [ANNOUNCE] Git v2.15.0-rc0 Junio C Hamano
2017-10-05 6:09 ` Jeff King [this message]
2017-10-05 13:10 ` Johannes Schindelin
2017-10-05 17:28 ` Stefan Beller
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=20171005060922.o2wzccm4uqq5o74e@sigill.intra.peff.net \
--to=peff@peff.net \
--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 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.