git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Soffian <jaysoffian@gmail.com>
To: "Hrvoje Nikšić" <hniksic@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Make "terminator behavior" the default with --pretty=format: ?
Date: Tue, 22 Feb 2011 17:41:01 -0500	[thread overview]
Message-ID: <AANLkTimLGqnxUygBUY6A=gpCa5gbT-g0L7ikW3Xbf+=_@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikGYOdJNGNXR1egPyMBhKpT=bby5fmr8MR9QTXt@mail.gmail.com>

On Tue, Feb 22, 2011 at 11:51 AM, Hrvoje Nikšić <hniksic@gmail.com> wrote:
> On Tue, Feb 22, 2011 at 5:43 PM, Will Palmer <wmpalmer@gmail.com> wrote:
>> On Tue, 2011-02-22 at 16:43 +0100, Hrvoje Nikšić wrote:
>>> Is there a reason, other than backward compatibility, for
>>> "--prety=format:" to have separator rather than terminator semantics?
>>
>> The "default behaviour" is the behaviour which occurs when one /doesn't/
>> specify something. For example: --pretty="%H %an" uses terminator
>> semantics.
>
> I didn't know that you could simply omit the "format:". Is it
> documented anywhere? The docs say:
>
>       --pretty[=<format>], --format[=<format>]
>           Pretty-print the contents of the commit logs in a given
> format, where <format> can be one of oneline, short,
>           medium, full, fuller, email, raw and format:<string>. When
> omitted, the format defaults to medium.

In the tformat section is:

 "In addition, any unrecognized string that has a % in it is
interpreted as if it has tformat: in front of it."

Of course, you need to know to read that far into the man page to find
that sentence, and the earlier summary of --pretty never gives any
hint to do so.

Mind submitting a documentation patch?

j.

      reply	other threads:[~2011-02-22 22:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 15:43 Make "terminator behavior" the default with --pretty=format: ? Hrvoje Nikšić
2011-02-22 16:43 ` Will Palmer
2011-02-22 16:51   ` Hrvoje Nikšić
2011-02-22 22:41     ` Jay Soffian [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='AANLkTimLGqnxUygBUY6A=gpCa5gbT-g0L7ikW3Xbf+=_@mail.gmail.com' \
    --to=jaysoffian@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=hniksic@gmail.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).