git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Cornelius <c.r1@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Bug report - git show <tagname> together with --pretty=format
Date: Wed, 08 Apr 2009 17:28:21 +0200	[thread overview]
Message-ID: <49DCC295.7010908@drmicha.warpmail.net> (raw)
In-Reply-To: <49DC9F07.4090105@gmx.de>

Cornelius venit, vidit, dixit 08.04.2009 14:56:
> Hi,
> I've a problem with git 1.6.2.2 (self compiled) and git show. I use it's 
> output for parsing the git data, so this is more than a minor issue for 
> me. When you normally do a git show on a tag name it's output resembles 
> the following:
> tag <tagname>
> Tagger: Cornelius <c.r1@gmx.de>
> Date:   Wed Apr 8 14:39:17 2009 +0200
> 
> 
> tagmessage
> commit 77e312e0527f87604e4c70ebf6040e79bb55d2ed
> <snip>
> 
> Now when you do a git show <tagname> 
> --pretty=format:"ENDOFGITTAGOUTPUTMESAGEHERE%n%H" --
> the Date: line is missing. Git 1.6.0.5 (which is avaible in my distro's 
> repos) doesn't have this issue. Please CC me, I'm not subcribed here.
> Cornelius

It's not a bug, it's a feature ;)

In fact, git show used to ignore format specifiers for the tag part and
apply them to the commit part only. Since
ea718e6 (show <tag>: reuse pp_user_info() instead of duplicating code,
2009-01-02)
(which is in v1.6.2) it applies the format to both, which is why there
is no tag date unless you ask for it (or use the default format).

Michael

  reply	other threads:[~2009-04-08 15:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 12:56 Bug report - git show <tagname> together with --pretty=format Cornelius
2009-04-08 15:28 ` Michael J Gruber [this message]
2009-04-08 16:37   ` Santi Béjar
2009-04-08 19:47     ` Plumbing commands (was: Bug report - git show <tagname> together with --pretty=format) Teemu Likonen

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=49DCC295.7010908@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=c.r1@gmx.de \
    --cc=git@vger.kernel.org \
    /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).