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

From: Ramsay Jones <ramsay@ramsayjones.plus.com>
Date: Jul 31, 2017, 23:36 UTC
Message-ID: <232547ab-3b87-debc-36a4-d2285ec10a06@ramsayjones.plus.com>
In-Reply-To: <xmqqfudcgryb.fsf@gitster.mtv.corp.google.com>

On 31/07/17 23:30, Junio C Hamano wrote: [snip]

Show 16 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'.
> 
>  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'.

I wouldn't normally comment on an issue like this because I am not very good at specifying, designing and evaluating UIs (so who in their right mind would listen to me). ;-)

FWIW, I suspect that I would not like using this interface either and would, therefore, not use it. However, I guess the worst that would happen, is that it would gain another 'wort' (--option) to turn off the "switches to backup" branch. :-D

I didn't want you to think that the lack of comments on this was because everybody agreed that it was a good idea.

ATB, Ramsay Jones