git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [PATCH] show --continue/skip etc. consistently in synopsis
Date: Mon, 17 Jun 2019 15:35:32 -0700	[thread overview]
Message-ID: <xmqqfto7suvf.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <991b0908-4ec5-2d19-4df3-df3eb28632c2@gmail.com> (Phillip Wood's message of "Mon, 17 Jun 2019 10:15:25 +0100")

Phillip Wood <phillip.wood123@gmail.com> writes:

> I'm not sure I'd argue too hard one way or the other, but I do think the
> documentation for the various commands should try to be consistent and
> the am, cherry-pick, rebase and revert man pages all use a single line
> for these options (although rebase is missing the parentheses).

Good.  Then please write these names in the proposed log message;
the version I commented on looked a bit strange to single out "am",
as if we are siding on a minority, but writing the names of its
friends that share the convention would not give that wrong
impression to the readers.

Thanks.

  reply	other threads:[~2019-06-17 22:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-16 13:24 [PATCH] show --continue/skip etc. consistently in synopsis Phillip Wood
2019-06-16 22:33 ` Junio C Hamano
2019-06-17  9:15   ` Phillip Wood
2019-06-17 22:35     ` Junio C Hamano [this message]
2019-06-17  2:02 ` Elijah Newren
2019-06-17  9:11   ` Phillip Wood
2019-06-17  9:17 ` [PATCH v2] " Phillip Wood

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqfto7suvf.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=phillip.wood123@gmail.com \
    --cc=phillip.wood@dunelm.org.uk \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).