git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Brian Swetland <swetland@google.com>
Cc: git@vger.kernel.org
Subject: Re: something like git-for-each-ref's --format for commits?
Date: Sun, 6 Jan 2008 04:05:07 -0500	[thread overview]
Message-ID: <20080106090507.GA10965@coredump.intra.peff.net> (raw)
In-Reply-To: <20080106085221.GA1729@bulgaria.corp.google.com>

On Sun, Jan 06, 2008 at 12:52:21AM -0800, Brian Swetland wrote:

> The --pretty=format:... option for git-log, etc has the annoying
> property of giving you <unknown> instead of an empty string if an
> item isn't example (say if you use %b on a commit with no body).
> 
> Am I missing some obvious solution here?  

I think --pretty=format: is what you are looking for. The "<unknown>"
behavior is fixed in the upcoming v1.5.4 (you get the empty string for
your example).

-Peff

      reply	other threads:[~2008-01-06  9:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-06  8:52 something like git-for-each-ref's --format for commits? Brian Swetland
2008-01-06  9:05 ` Jeff King [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=20080106090507.GA10965@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=swetland@google.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).