From: Andreas Ericsson <ae@op5.se>
To: Lars Hjemli <hjemli@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] Skip excessive blank lines before commit body
Date: Thu, 04 Jan 2007 16:50:54 +0100 [thread overview]
Message-ID: <459D225E.4010208@op5.se> (raw)
In-Reply-To: <11678312532251-git-send-email-hjemli@gmail.com>
Lars Hjemli wrote:
> This modifies pretty_print_commit() to make the output of git-rev-list and
> friends a bit more predictable.
>
> A commit body starting with blank lines might be unheard-of, but still possible
> to create using git-commit-tree (so is bound to appear somewhere, sometime).
>
Lovely. I was just looking in to doing the exact same thing myself.
For reference, there is a tool somewhere that creates CVS commit
messages with an empty title-line. When imported to git, those empty
lines remain and fuzz up gitk and qgit viewing ad nauseum. I'm guessing
(and hoping) this patch would take care of it.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
prev parent reply other threads:[~2007-01-04 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 13:34 [PATCH] Skip excessive blank lines before commit body Lars Hjemli
2007-01-03 17:03 ` Junio C Hamano
2007-01-04 15:50 ` Andreas Ericsson [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=459D225E.4010208@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=hjemli@gmail.com \
--cc=junkio@cox.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