From: Jon Loeliger <jdl@freescale.com>
To: Stephan Beyer <s-beyer@gmx.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [PATCH v2] git-commit.txt: Correct option alternatives
Date: Sat, 07 Jun 2008 20:36:54 -0500 [thread overview]
Message-ID: <484B37B6.1040408@freescale.com> (raw)
In-Reply-To: <1212836805-20684-1-git-send-email-s-beyer@gmx.net>
Stephan Beyer wrote:
> This patch fixes the SYNOPSIS in git-commit.txt:
> * --amend is not an alternative option to -c/-C/-F/-m
> * -m and -F are not alternative options to -c/-C,
> because you can reuse authorship from a commit (-c/-C)
> but change the message (-m/-F).
>
> Furthermore, for long-option consistency --author <author>
> is changed to --author=<author>.
>
> Signed-off-by: Stephan Beyer <s-beyer@gmx.net>
> ---author <author>::
> +--author=<author>::
> Override the author name used in the commit. Use
> `A U Thor <author@example.com>` format.
>
Hey Junio,
Say, if we were to document and espouse one form over the other,
which would you recommend or prefer?
jdl
next prev parent reply other threads:[~2008-06-08 1:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 0:24 [PATCH 1/2] git-commit.txt: Correct option alternatives Stephan Beyer
2008-06-07 0:24 ` [PATCH 2/2] git-commit.txt: Add missing long/short options Stephan Beyer
2008-06-07 21:05 ` Junio C Hamano
2008-06-08 1:36 ` [PATCH 1/5] " Stephan Beyer
2008-06-08 1:36 ` [PATCH 2/5] Docs: Use "-l::\n--long\n" format in OPTIONS sections Stephan Beyer
2008-06-08 1:36 ` [PATCH 3/5] Docs: add some long/short options Stephan Beyer
2008-06-08 1:36 ` [PATCH 4/5] git-describe.txt: document --always Stephan Beyer
2008-06-08 1:36 ` [PATCH 5/5] git-name-rev.txt: document --no-undefined and --always Stephan Beyer
2008-06-07 3:34 ` [PATCH 1/2] git-commit.txt: Correct option alternatives Christian Couder
2008-06-07 11:06 ` [PATCH v2] " Stephan Beyer
2008-06-08 1:36 ` Jon Loeliger [this message]
2008-06-08 4:23 ` Jeff King
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=484B37B6.1040408@freescale.com \
--to=jdl@freescale.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=s-beyer@gmx.net \
/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).