From: Jonathan Nieder <jrnieder@gmail.com>
To: Cliff Frey <cliff@meraki.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] documentation: git-config minor cleanups
Date: Sun, 17 Oct 2010 22:38:33 -0500 [thread overview]
Message-ID: <20101018033722.GA3340@burratino> (raw)
In-Reply-To: <1287371445-26134-1-git-send-email-cliff@meraki.com>
Cliff Frey wrote:
> Change push.default's description to add hyphens between values and
> descriptions to make the manpage easier to read. The html version is
> readable either way.
>
> Change status.showUntrackedFiles to make item descriptions be
> sentences and to use the same asciidoc format as push.default.
Yep, it is hard to read
| · nothing do not push anything.
|
| · matching push all matching branches. All
| branches having the same name in both ends are
[etc]
without the font change to indicate where each term begins and ends.
So for what it's worth:
Acked-by: Jonathan Nieder <jrnieder@gmail.com>
Thanks.
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -1765,9 +1765,9 @@ status.showUntrackedFiles::
> the untracked files. Possible values are:
> +
> --
> - - 'no' - Show no untracked files
> - - 'normal' - Shows untracked files and directories
> - - 'all' - Shows also individual files in untracked directories.
> +* `no` - Show no untracked files.
> +* `normal` - Shows untracked files and directories.
> +* `all` - Shows also individual files in untracked directories.
If you are making these into sentences, they should be
- Show no untracked...
- Show untracked...
- Also show...
, no? [i.e., s/Shows/Show/c]
prev parent reply other threads:[~2010-10-18 3:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 3:10 [PATCH] documentation: git-config minor cleanups Cliff Frey
2010-10-18 3:38 ` Jonathan Nieder [this message]
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=20101018033722.GA3340@burratino \
--to=jrnieder@gmail.com \
--cc=cliff@meraki.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).