Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 25, 2017, 00:40 UTC
Message-ID: <xmqq7ewnhaps.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CALiud+mjN=cTg_CXWNWnE=0N5RiT-FEN5JMGbYW0byMbmexQvQ@mail.gmail.com>

Sahil Dua <sahildua2305@gmail.com> writes:

Show 11 quoted lines

> On Fri, Sep 22, 2017 at 5:39 AM, Junio C Hamano <gitster@pobox.com> wrote:
>>
>> So here is such an update.  As the topic is not in 'next' yet, it
>> could also be implemented by replacing patch(es) in the series, but
>> doing it as a follow-up fix made it easier to see what got changed
>> (both in the code and in the tests), so that is how I decided to do
>> this patch.
>>
> Awesome! Thanks for the patch. It was easier than I'd have expected it
> to be. Looks like it fixes the concerns of moving head. Is there
> anythign required from my side on this features / series of patches?

If you now agree with the updated behaviour and think it makes more sense that "git branch -c new HEAD" does not check out 'new', then there is nothing required. Well, other than the usual finding, reporting and optionally fixing bugs in the documentation and the code, that is ;-)

Thanks.