From: Junio C Hamano <gitster@pobox.com>
To: Sergey Organov <sorganov@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Why git branch --show-current ignores -v?
Date: Fri, 26 Dec 2025 11:11:49 +0900 [thread overview]
Message-ID: <xmqq1pkim1p6.fsf@gitster.g> (raw)
In-Reply-To: <xmqq8qeqm1tp.fsf@gitster.g> (Junio C. Hamano's message of "Fri, 26 Dec 2025 11:09:06 +0900")
Junio C Hamano <gitster@pobox.com> writes:
> Sergey Organov <sorganov@gmail.com> writes:
>
>> It looks useful and natural for "git branch --show-current -v[v]" to
>> verbosely describe current branch, similar to what --list does. Is there
>> sound reason why -v is not supported by --show-current?
>
> The "--show-current" feature was invented merely for those who
> somehow found it ugly to use "git symbolic-ref HEAD" when a user
> wants to learn what the current branch was. If I have to guess,
> nobody thought about it as a way to get the same output as "--list"
> but restricted to the single current branch. Hence nobody felt the
> need to support any option that the "--list" operation supported,
> including "-v". IOW, nobody shared your "It looks useful" so far,
> especially among the people who knew where the "--show-current"
> option came from.
>
> I do not think anybody terribly objects if somebody teaches "-v" to
> make "git branch --show-current" more verbose, and other "--list"
> operations in general, but I suspect that the exact contents in the
> verbose output may have to be different from that of "--list". For
> one thing, as "--show-current" limits its output to the current
> branch, the two-place indent "git branch --list" gives its output is
> not there, and "-v" would probably not want to add it.
Forgot to say something much more important.
Commands should complain when users give them input that they do not
understand. If "git branch --show-current -v" silently eats "-v", I
would say it is a bug.
Unless we define that the current output is already verbose, that
is.
Thanks.
next prev parent reply other threads:[~2025-12-26 2:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 16:08 Why git branch --show-current ignores -v? Sergey Organov
2025-12-26 2:09 ` Junio C Hamano
2025-12-26 2:11 ` Junio C Hamano [this message]
2025-12-26 3:28 ` [PATCH] branch: Remove unnecessary verbose flag K Jayatheerth
2025-12-26 4:15 ` Junio C Hamano
2025-12-26 15:43 ` Why git branch --show-current ignores -v? Sergey Organov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq1pkim1p6.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sorganov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.