Re: Git for Windows v2.20.0-rc0, was Re: [ANNOUNCE] Git v2.20.0-rc0
- Date: Wed, 21 Nov 2018 09:20:26 -0500
- From: Jeff King <peff@xxxxxxxx>
- Subject: Re: Git for Windows v2.20.0-rc0, was Re: [ANNOUNCE] Git v2.20.0-rc0
On Tue, Nov 20, 2018 at 03:17:07PM -0800, Bryan Turner wrote:
> I've run 2.20.0-rc0 through the test matrix for Bitbucket Server on
> both Linux and Windows, and the only failures were related to this
> * "git branch -l <foo>" used to be a way to ask a reflog to be
> created while creating a new branch, but that is no longer the
> case. It is a short-hand for "git branch --list <foo>" now.
> Since this is an intentional change I suspect there's nothing to do
> for it but patch Bitbucket Server and move on, but I'll confess it's a
> little frustrating that the option was deprecated in 2.19 and then
> immediately removed in the next minor release. Such a
> backwards-incompatible change seems far more apt for a major release,
> a perspective that's reinforced by having the change follow such a
> brief deprecation period--2.19.0 was only tagged September 10th (in my
> timezone), so it's been less than 3 months. (Looking at the git branch
> documentation for 2.18.0  shows nothing about this deprecation; the
> messaging first appears in 2.19.0 . To be honest, I didn't even
> realize it was deprecated until now, when it's gone--our test suite is
> automated, so the deprecation warning was not visible.)
We did go a bit faster than usual, under the assumption that nobody's
really using "-l". It has been the default since 2006.
Can you tell us a little more about your invocation?
We still have time to avoid the change for this release. And this early
testing of master and release candidates is wonderful exactly to get
this kind of feedback before it's too late.