From: Marc Branchaud <marcnarc@xiplink.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>,
Junio C Hamano <gitster@pobox.com>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH] log: document the --decorate=auto option
Date: Fri, 27 May 2016 14:35:18 -0400 [thread overview]
Message-ID: <57489366.507@xiplink.com> (raw)
In-Reply-To: <57486E12.7030907@ramsayjones.plus.com>
On 2016-05-27 11:56 AM, Ramsay Jones wrote:
>
> Signed-off-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
> ---
>
> Hi Junio,
>
> While reading an email from Linus earlier (RFC: dynamic "auto" date formats),
> I noticed that log.decorate was being set to 'auto'. Since I didn't recall
> that setting (even if it's easy to guess), I went looking for the documentation ...
>
> This should probably be marked RFC, since I haven't checked that the formatting
> is OK (I don't have the documentation toolchain installed these days).
>
> ATB,
> Ramsay Jones
>
> Documentation/config.txt | 5 ++++-
> Documentation/git-log.txt | 8 +++++---
> 2 files changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/config.txt b/Documentation/config.txt
> index 53f00db..0707b3b 100644
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -1956,7 +1956,10 @@ log.decorate::
> command. If 'short' is specified, the ref name prefixes 'refs/heads/',
> 'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is
> specified, the full ref name (including prefix) will be printed.
> - This is the same as the log commands '--decorate' option.
> + If 'auto' is specified, then if the output is going to a terminal,
> + the ref names are shown as if 'short' were given, otherwise no ref
> + names are shown. This is the same as the log commands '--decorate'
s/commands/command's/
M.
next prev parent reply other threads:[~2016-05-27 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 15:56 [PATCH] log: document the --decorate=auto option Ramsay Jones
2016-05-27 18:35 ` Marc Branchaud [this message]
2016-05-27 20:17 ` 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=57489366.507@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ramsay@ramsayjones.plus.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).