git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Michael Dressel <MichaelTiloDressel@t-online.de>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] add '%d' pretty format specifier to show decoration
Date: Wed, 03 Sep 2008 13:59:17 -0700	[thread overview]
Message-ID: <7vsksh9c9m.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080903203616.GB32223@coredump.intra.peff.net> (Jeff King's message of "Wed, 3 Sep 2008 16:36:16 -0400")

Jeff King <peff@peff.net> writes:

> On Wed, Sep 03, 2008 at 01:10:12PM -0700, Junio C Hamano wrote:
>
>> I agree with the above reasoning.  If we go with surrounding parentheses,
>> it might even make sense to include a SP _before_ the opening parenthesis,
>> so that "%h %s%d" expands to either of these:
>> 
>>    $ git show -s --pretty=format:'%h %s%d' v1.6.0^0 v1.6.0^1
>>    ea02eef GIT 1.6.0 (refs/tags/v1.6.0)
>>    373a273 Merge git-gui 0.11.0
>
> Isn't that what you argued against in Dscho's version of the patch?
>
>     http://mid.gmane.org/7v1w5exfwb.fsf@gitster.siamese.dyndns.org

Yeah, but unlike Linus, I am not infallible.  Also, I can change my mind.

If the concensus is that we do the simpler variant _now_ and leave
extending it for later, I think it is Ok to pick any one reasonable
default/simple format, and including the parentheses (with leading SP)
would be one reasonable default, certainly more reasonable than not
including the parentheses at all.

The background is somewhat different, too.

Back then I didn't think anybody but Dscho was interested in including
decorate in --pretty=format in half-baked form.  René is comment was to do
more flexible but complex variant.  I didn't see many people wanted to
have it in "limited but usable for simpler needs" form.

It wasn't that urgent, as opposed to this round more people seem to be
interested in having it even in a limited form.  And I knew Dscho was very
much capable of doing the "going whole nine yards" version, instead of a
simple-limited one.  "If we can afford to spend time to get it right in
the first round why not?" was part of the reasons behind my objection.

  reply	other threads:[~2008-09-03 21:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 18:40 [PATCH 1/2] add '%d' pretty format specifier to show decoration Michael Dressel
2008-09-03 19:12 ` Jeff King
2008-09-03 20:10   ` Junio C Hamano
2008-09-03 20:36     ` Jeff King
2008-09-03 20:59       ` Junio C Hamano [this message]
2008-09-03 21:04         ` Jeff King
2008-09-03 22:06         ` René Scharfe
2008-09-04  3:51           ` Jeff King
2008-09-04 15:47             ` René Scharfe
2008-09-04 21:38               ` [PATCH 1/3] log: add load_ref_decorations() René Scharfe
2008-09-04 21:39               ` [PATCH 2/3] move load_ref_decorations() to log-tree.c and export it René Scharfe
2008-09-04 21:40               ` [PATCH 3/3] add '%d' pretty format specifier to show decoration René Scharfe
2008-09-05  0:11                 ` Jeff King
2008-09-05  0:28                   ` Junio C Hamano
2008-09-05  0:37                     ` Jeff King
2008-09-05  0:41                       ` Junio C Hamano
2008-09-05 18:38                     ` Michael Dressel
2008-09-09 17:33                       ` Michael Dressel
2008-09-09 20:15                         ` René Scharfe
2008-09-05 16:14                   ` René Scharfe
2008-09-03 19:17 ` [PATCH 1/2] " Jeff King
2008-09-03 20:06   ` Michael Dressel
2008-09-03 20:33     ` Jeff King

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=7vsksh9c9m.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=MichaelTiloDressel@t-online.de \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).