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

From: Sahil Dua <sahildua2305@gmail.com>
Date: Aug 3, 2017, 20:17 UTC
Message-ID: <CALiud+nKTNsr_z528Wwv3ELLk+uKoJkYa8hctg-C1dtXrbkvKg@mail.gmail.com>
In-Reply-To: <xmqqfudcgryb.fsf@gitster.mtv.corp.google.com>

Show 11 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?

Show 6 quoted lines

>
>  I personally do not think "branch --copy master backup" while on
>  "master" that switches to "backup" is a good UI, and I *will* say
>  "I told you so" when users complain after we merge this down to
>  'master'.
>