git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix formatting in git-config(1)
Date: Thu, 21 Jun 2012 01:05:12 +0200	[thread overview]
Message-ID: <m2r4t94maf.fsf@igel.home> (raw)
In-Reply-To: <7v4nq5twwg.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Wed, 20 Jun 2012 15:56:47 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> Andreas Schwab <schwab@linux-m68k.org> writes:
>
>> Remove the open block markers from the status.showUntrackedFiles entry
>> as they cause all remaining entries to be indented one level too much.
>
> Hrm...
>
> I looked at http://git-htmldocs.googlecode.com/git/git-config.html
> and am unsure what "one level too much" you are referring to.

I'm using asciidoc 8.4.5.  Probably version dependent.

> Also looking at the output from
>
> $ git config --help
>
> I see (RHS end truncated to avoid line wrapping in MUA):

This is what I see:

       status.showUntrackedFiles
           By default, git-status(1) and git-commit(1) show files which are
           not currently tracked by Git. Directories which contain only
           untracked files, are shown with the directory name only. Showing
           untracked files means that Git needs to lstat() all all the files
           in the whole repository, which might be slow on some systems. So,
           this variable controls how the commands displays the untracked
           files. Possible values are:

           ·    no - Show no untracked files.

           ·    normal - Show untracked files and directories.

           ·    all - Show also individual files in untracked directories.
               If this variable is not specified, it defaults to normal. This
               variable can be overridden with the -u|--untracked-files option
               of git-status(1) and git-commit(1).

           status.submodulesummary
               Defaults to false. If this is set to a non zero number or true
               (identical to -1 or an unlimited number), the submodule summary
               will be enabled and a summary of commits for modified
               submodules will be shown (see --summary-limit option of git-
               submodule(1)).


Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2012-06-20 23:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 22:49 [PATCH] Fix formatting in git-config(1) Andreas Schwab
2012-06-20 22:56 ` Junio C Hamano
2012-06-20 23:05   ` Andreas Schwab [this message]
2012-06-22 23:52   ` Junio C Hamano
2012-06-23  8:01     ` Andreas Schwab
2012-06-23  8:12       ` Junio C Hamano
2012-06-23  8:51         ` Andreas Schwab
2012-06-23 12:29         ` Andreas Schwab
2012-06-23 18:27           ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2012-06-23 13:18 Andreas Schwab
2012-07-03 19:23 ` Junio C Hamano

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=m2r4t94maf.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --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).