From: Junio C Hamano <gitster@pobox.com>
To: Stephan Beyer <s-beyer@gmx.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] git-commit.txt: Add missing long/short options
Date: Sat, 07 Jun 2008 14:05:24 -0700 [thread overview]
Message-ID: <7vy75hlzvv.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 1212798261-26785-2-git-send-email-s-beyer@gmx.net
Stephan Beyer <s-beyer@gmx.net> writes:
> Furthmore, use
> short option::
> long option::
> instead of
> short option|long option::
> and split the "-c or -C <commit>" item into two separate items.
> ...
> --q|--quiet::
> +-q::
> +--quiet::
While this may result in easier-to-read output, there are tons of other
pages that follow the current style. I'd prefer:
(1) a patch without "a|b\n" => "a::\nb::" for only git-commit.txt and
(2) a patch that is "a|b\n" => "a::\nb::" for everybody but without any
other changes.
next prev parent reply other threads:[~2008-06-07 21:06 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 [this message]
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
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=7vy75hlzvv.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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).