Re: What's cooking in git.git (Jul 2017, #09; Mon, 31)

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 3, 2017, 21:17 UTC
Message-ID: <xmqq8tj0wdtz.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CALiud+nKTNsr_z528Wwv3ELLk+uKoJkYa8hctg-C1dtXrbkvKg@mail.gmail.com>

Sahil Dua <sahildua2305@gmail.com> writes:

Show 15 quoted lines

>>
>> * sd/branch-copy (2017-06-18) 3 commits
>>   (merged to 'next' on 2017-07-18 at 5e3b9357ea)
>>  + branch: add a --copy (-c) option to go with --move (-m)
>>  + branch: add test for -m renaming multiple config sections
>>  + config: create a function to format section headers
>>
>>  "git branch" learned "-c/-C" to create and switch to a new branch
>>  by copying an existing one.
>>
>>  Will cook in 'next'.
>
> Junio, are we still waiting for interaction with other patches to
> settle down or simply cooking it further for any potential
> feedback/suggestions on this?

No, "waiting for other topics to settle" was a long time ago. During the pre-release feature freeze, nothing will be merged to 'master', unless it is a trivially correct bugfix or a regression fix. This one is neither.