git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Marco Costalba <mcostalba@gmail.com>
Cc: Lars Hjemli <hjemli@gmail.com>, Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Possible regression in git-rev-list --header
Date: Thu, 04 Jan 2007 16:18:23 +0100	[thread overview]
Message-ID: <459D1ABF.8010500@op5.se> (raw)
In-Reply-To: <e5bfff550701030235g6f26044h8dd73e8abe1ec9e3@mail.gmail.com>

Marco Costalba wrote:
> On 1/3/07, Lars Hjemli <hjemli@gmail.com> wrote:
>> On 1/3/07, Marco Costalba <mcostalba@gmail.com> wrote:
>> >         - one blank line
>> >         - zero or one line with log title
>> >         - zero or more lines with log message
>> >         - a terminating '\0'
>>
>> I think the should be:
>>   -zero or more blank lines
> 
> Isn't it zero or _one_ blank line? Why more then one? would be it
> useful? surely is slower to parse.
> 

I've imported a repository from CVS to git (the nagiosplugin repo), 
where one author consistently put an empty line before the "commit 
subject". I'm fairly certain this is done by the tool he uses (some GUI 
thing, no doubt).

I'm currently looking into stripping optional empty lines appearing 
postheaders-prebody from rev-list output, as it completely fudges qgit 
and gitk viewing alike. Good thing the author in question only does 
translations and no code work, or I'd be screaming with frustration 
trying to figure out which commit does what. Mind you, CVS's lack of 
forensic tools doesn't exactly inspire the clear and concise commit 
messages we see in git, but still...


>>   -zero or more non-blank lines with log title
> 
> multi lines titles are allowed? never saw one of them.
> 

They aren't disallowed. The log message part only by convention consists 
of a title line followed by a blank and then the message body. It's 
entirely possible to just start writing the message straight off, or put 
any number of blank lines wherever.

>>   -zero or more blank lines
> 
> Why? this is necessary only to disambiguate muti (non blank) lines
> titles, but as Junio pointed out distinction between log title and log
> message is only in the Porcelain, not encoded in git. So the Porcalain
> is going to show _one_line title if any an the remaining stuff in the
> log message.
> 

Sensible. There's no (reliable) way of knowing if the first line with 
text on is actually a title or just the start of a 25-line sentence, or 
even the signoff line, or completely empty.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

  parent reply	other threads:[~2007-01-04 15:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-30 17:56 Possible regression in git-rev-list --header Marco Costalba
2006-12-30 18:30 ` Jakub Narebski
2006-12-30 18:57 ` Johannes Schindelin
2006-12-30 20:20   ` Junio C Hamano
2006-12-30 22:19     ` Junio C Hamano
2006-12-31  1:13       ` Johannes Schindelin
2006-12-31  1:45         ` Junio C Hamano
2006-12-31 11:45           ` Marco Costalba
2006-12-31 15:27             ` Johannes Schindelin
2006-12-31 15:43               ` Marco Costalba
2007-01-01  3:21                 ` Junio C Hamano
2007-01-02 21:32                   ` Johannes Schindelin
2007-01-02 22:13                     ` Junio C Hamano
2007-01-02 22:28                       ` Johannes Schindelin
2007-01-02 22:29                       ` Marco Costalba
2007-01-03  9:21                   ` Marco Costalba
2007-01-03 10:10                     ` Junio C Hamano
2007-01-03 10:21                     ` Lars Hjemli
2007-01-03 10:35                       ` Marco Costalba
2007-01-03 11:14                         ` Lars Hjemli
2007-01-04 15:21                           ` Andreas Ericsson
2007-01-04 15:18                         ` Andreas Ericsson [this message]
2007-01-03 10:38                       ` Lars Hjemli
2006-12-31  0:37     ` Johannes Schindelin
2006-12-30 20:22   ` [PATCH] Move commit reencoding parameter parsing to revision.c Junio C Hamano
2006-12-31  1:10     ` Johannes Schindelin

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=459D1ABF.8010500@op5.se \
    --to=ae@op5.se \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=hjemli@gmail.com \
    --cc=junkio@cox.net \
    --cc=mcostalba@gmail.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).