Re: [PATCH] branch -l: print useful info whilst rebasing a non-local branch

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 25, 2018, 17:06 UTC
Message-ID: <xmqq7eq0f5ju.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <20180325043337.GA32465@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 6 quoted lines

> IMHO we should do one of:
>
>   1. Nothing. ;)
>
>   2. Complain about "-l" in list mode to help educate users about the
>      current craziness.

Nah. We've seen this, perhaps not often but enough times over long period of time. The above two would not fly as a longer term solution.

Show 10 quoted lines

>
>   3. Drop "-l" (probably with a deprecation period); it seems unlikely
>      to me that anybody uses it for branch creation, and this would at
>      least reduce the confusion (then it would just be "so why don't we
>      have -l" instead of "why is -l not what I expect").
>
>   4. Repurpose "-l" as a shortcut for --list (also after a deprecation
>      period). This is slightly more dangerous in that it may confuse
>      people using multiple versions of Git that cross the deprecation
>      line. But that's kind of what the deprecation period is for...

3. is prerequisite for 4.  If we haven't gone through both in 5
years we should be ashamed of ourselves ;-)  But at least we should
start 3. and aim to finish 3. in 2 years if not sooner.