From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] symbolic-ref: teach "--[no-]recurse" option
Date: Sat, 08 Oct 2022 21:41:02 -0700 [thread overview]
Message-ID: <xmqqr0zha9sx.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cQHw_VjbA2_HaZJj3Q0v8C6uUukr40vXFuizx4M_04XFA@mail.gmail.com> (Eric Sunshine's message of "Sat, 8 Oct 2022 00:54:36 -0400")
Eric Sunshine <sunshine@sunshineco.com> writes:
> With his recent documentation-normalization work, I suspect Ævar would
> appreciate an update to the synopsis, as well:
>
> SYNOPSIS
> --------
> [verse]
> 'git symbolic-ref' [-m <reason>] <name> <ref>
> -'git symbolic-ref' [-q] [--short] <name>
> +'git symbolic-ref' [-q] [--short] [--no-recurse] <name>
> 'git symbolic-ref' --delete [-q] <name>
>
> or something similar (i.e. plain [--recurse] or composite
> [--[no-]-recurse] or [--recurse | --no-recurse]).
Yeah, that looks good.
I checked the in-code usage that used [<options>] (hence I didn't
have to do anything new), but apparently forgot about the doc.
As there is (and there will ever be) no configuration knob for this
plumbing command to make the non-recursive behaviour the default, I
think listing [--no-recurse] alone, not [--[no-]recurse], would be
the right thing to do in the documentation.
Thanks.
next prev parent reply other threads:[~2022-10-09 4:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 22:00 [PATCH] symbolic-ref: teach "--[no-]recurse" option Junio C Hamano
2022-10-08 3:35 ` Eric Sunshine
2022-10-08 4:20 ` Junio C Hamano
2022-10-08 4:34 ` [PATCH v2] " Junio C Hamano
2022-10-08 4:54 ` Eric Sunshine
2022-10-09 4:41 ` Junio C Hamano [this message]
2022-10-08 9:37 ` Bagas Sanjaya
2022-10-09 12:47 ` Junio C Hamano
2022-10-08 12:28 ` Philip Oakley
2022-10-08 15:28 ` Philip Oakley
2022-10-09 12:07 ` Junio C Hamano
2022-10-11 14:49 ` Philip Oakley
2022-10-09 22:13 ` [PATCH v3] " 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=xmqqr0zha9sx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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;
as well as URLs for NNTP newsgroup(s).