Re: [PATCH v2] Documentation: Fix indentation problem in git-commit(1)
- From
Jacob Helwig <jacob.helwig@gmail.com>
- Date
- Feb 19, 2010, 17:54 UTC
- Message-ID
- <20100219175411.GA388@vfb-9.home>
- In-Reply-To
- <1266237186-8065-1-git-send-email-jacob.helwig@gmail.com>
On 04:33 Mon 15 Feb , Jacob Helwig wrote:
Show 46 quoted lines
> Ever since the "See linkgit:git-config[1]..." paragraph was added to the > description for --untracked-files (d6293d1), the paragraphs for the > following options were indented at the same level as the "See > linkgit:git-config[1]" paragraph. This problem showed up in the > manpages, but not in the HTML documentation. > > While this does fix the alignment of the options following > --untracked-files in the manpage, the "See linkgit..." portion of the > description does not retain its previous indentation level in the > manpages, or HTML documentation. > > Signed-off-by: Jacob Helwig <jacob.helwig@gmail.com> > Acked-by: Thomas Rast <trast@student.ethz.ch> > --- > > When adding the caveat to the commit message, the introductory comment > paragraph I had before seemed to fit better; I decided to go with a > version of it, instead. > > Documentation/git-commit.txt | 6 +++--- > 1 files changed, 3 insertions(+), 3 deletions(-) > > diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt > index e99bb14..64fb458 100644 > --- a/Documentation/git-commit.txt > +++ b/Documentation/git-commit.txt > @@ -197,13 +197,13 @@ FROM UPSTREAM REBASE" section in linkgit:git-rebase[1].) > Show untracked files (Default: 'all'). > + > The mode parameter is optional, and is used to specify > -the handling of untracked files. The possible options are: > +the handling of untracked files. > ++ > +The possible options are: > + > --- > - 'no' - Show no untracked files > - 'normal' - Shows untracked files and directories > - 'all' - Also shows individual files in untracked directories. > --- > + > See linkgit:git-config[1] for configuration variable > used to change the default for when the option is not > -- > 1.7.0 >
I haven't seen any further discussion on this after I sent out a v2 with Thomas's suggested change to the commit message, and I didn't want to let the problem that this is trying to address fall through the cracks.
Does anyone have any comments on the v2 of this change?
-- Jacob Helwig