From: Eli Barzilay <eli@barzilay.org>
To: git@vger.kernel.org
Subject: Re: git rev-list formatting
Date: Tue, 23 Mar 2010 08:59:04 -0400 [thread overview]
Message-ID: <m3fx3rnqhz.fsf@winooski.ccs.neu.edu> (raw)
In-Reply-To: 20100323122603.GA2053@coredump.intra.peff.net
Jeff King <peff@peff.net> writes:
> On Tue, Mar 23, 2010 at 07:06:38AM -0400, Eli Barzilay wrote:
>
>> > [...]
>>
>> I've made a copy of the repository at
>>
>> http://tmp.barzilay.org/testing.git.tgz
>>
>> which shows what I said when I run
>>
>> git rev-list --pretty="%b" 267d60518
>> git rev-list --pretty="%b" 84482
>
> The problem is that most of those commits don't _have_ bodies.
> Remember that "%b" is about everything in the commit message after
> the first first paragraph.
*Ugh*... Yes, I've seen that a lot, yet somehow I managed to
completely miss it. Sorry about the noise.
> Now one might argue that rev-list should still put in the extra
> newline separator in this case. I haven't been paying attention, but
> hasn't that been discussed in another thread recently?
(That might have made it more confusing, but I should still have
guessed what's wrong...)
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
prev parent reply other threads:[~2010-03-23 12:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 11:30 git rev-list formatting Eli Barzilay
2010-03-22 11:39 ` Eli Barzilay
2010-03-22 13:08 ` Michael J Gruber
2010-03-22 13:36 ` [PATCH] rev-list: heed --abbrev-commit option Michael J Gruber
2010-03-26 19:32 ` Junio C Hamano
2010-03-27 13:30 ` Michael J Gruber
2010-03-22 14:42 ` git rev-list formatting Eli Barzilay
2010-03-22 17:22 ` René Scharfe
2010-03-23 1:57 ` Eli Barzilay
2010-03-23 10:52 ` Michael J Gruber
2010-03-23 11:06 ` Eli Barzilay
2010-03-23 12:26 ` Jeff King
2010-03-23 12:40 ` Erik Faye-Lund
2010-03-23 12:59 ` Eli Barzilay [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=m3fx3rnqhz.fsf@winooski.ccs.neu.edu \
--to=eli@barzilay.org \
--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).