public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: Alexander Shopov <ash@kambanaria.org>,
	git@vger.kernel.org, worldhello.net@gmail.com
Subject: Re: [PATCH  1/1] show-ref: improve short help messages of options
Date: Fri, 26 Jul 2024 14:28:02 +0200	[thread overview]
Message-ID: <ZqOWUrynjUN2A5TM@tanuki> (raw)
In-Reply-To: <xmqqr0bhldjp.fsf@gitster.g>

[-- Attachment #1: Type: text/plain, Size: 1823 bytes --]

On Thu, Jul 25, 2024 at 08:03:06AM -0700, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks.im> writes:
> 
> > Agreed, I think that this is a sensible change. In practice, this
> > feature can also be combined with `--head`, so in that spirit we might
> > even change it to:
> >
> >     "only show tags (can be combined with --branches and --head)"
> >
> > Not sure though whether this is getting too noisy?
> 
> It is somewhat an oxymoron that "*only* show X" can be combined with
> "*only* show Y" in the first place.

Yeah, this is the root of the problem why those braces are required in
the first place. But that being said, the option is somewhat funny
because it indeed limits what we show to only show tags. The fact that
it can be combined with other options to expand on what it shows doesn't
change that, so I think "only" is okay-ish even though it certainly is
not perfect.

> For a reader to accept it without finding it awkward, the reader
> must understand that
> 
>  (1) the command shows by default everything, but
> 
>  (2) if any of these "only show" options are given, the command
>      stops showing everything and the user can pick which subset of
>      "only show" options to give, which work additively.
> 
> But if the reader knows that much already, it is redundant to say
> "can be combined with", isn't it?

Hum. I personally find the way that this is worded intuitive and think
that I would find it helpful when reading it as a less-knowledgeable
user. But naturally, I'm quite biased and may be too unimaginative to
come up with a better wording.

Meanwhile, I think that the proposed change strictly improves this
message and thus don't see a reason not to take it. Unless we see
somebody come up with a less-awkward solution, that is.

Patrick

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-07-26 12:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-24 11:11 [PATCH 1/1] show-ref: improve short help messages of options Alexander Shopov
2024-07-25  7:15 ` Patrick Steinhardt
2024-07-25 15:03   ` Junio C Hamano
2024-07-26 12:28     ` Patrick Steinhardt [this message]
2024-07-26 15:46       ` Junio C Hamano

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=ZqOWUrynjUN2A5TM@tanuki \
    --to=ps@pks.im \
    --cc=ash@kambanaria.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=worldhello.net@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox