git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Possible regression in git-rev-list --header

From
LHLars Hjemli <hjemli@gmail.com>
Date
Jan 3, 2007, 11:14 UTC
Message-ID
<8c5c35580701030314t69b6a7dbhf9cb99de4567b93e@mail.gmail.com>
In-Reply-To
<e5bfff550701030235g6f26044h8dd73e8abe1ec9e3@mail.gmail.com>
On 1/3/07, Marco Costalba <mcostalba@gmail.com> wrote:
Show 12 quoted lines
> 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.

My point is just that the log message is unformatted. There is nothing stopping you from adding blank lines at the start of the message.

But then I tested it, and it seems as 'git-commit' strips off any leading blank lines (but git-commit-tree does not). So expecting one blank _might_ be good enough.

>
> >   -zero or more non-blank lines with log title
>
> multi lines titles are allowed? never saw one of them.
It is allowed (I tested this)
Show 8 quoted lines
>
> >   -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.

Well, if the porcelain chooses to do so, it probably is ok. But I think the parsing/presentation of the log title/message would be more correct/better formatted if the parser is more "adaptive" to the content.

-- 
larsh
Previous: Marco CostalbaNext: Andreas Ericsson
Message 20 of 26 in “Possible regression in git-rev-list --header”
  1. Marco CostalbaDec 30, 2006
  2. Jakub NarebskiDec 30, 2006
  3. Johannes SchindelinDec 30, 2006
  4. Junio C HamanoDec 30, 2006
  5. Junio C HamanoDec 30, 2006
  6. Johannes SchindelinDec 31, 2006
  7. Junio C HamanoDec 31, 2006
  8. Marco CostalbaDec 31, 2006
  9. Johannes SchindelinDec 31, 2006
  10. Marco CostalbaDec 31, 2006
  11. Junio C HamanoJan 1, 2007
  12. Johannes SchindelinJan 2, 2007
  13. Junio C HamanoJan 2, 2007
  14. Johannes SchindelinJan 2, 2007
  15. Marco CostalbaJan 2, 2007
  16. Marco CostalbaJan 3, 2007
  17. Junio C HamanoJan 3, 2007
  18. Lars HjemliJan 3, 2007
  19. Marco CostalbaJan 3, 2007
  20. Lars HjemliJan 3, 2007
  21. Andreas EricssonJan 4, 2007
  22. Andreas EricssonJan 4, 2007
  23. Lars HjemliJan 3, 2007
  24. Johannes SchindelinDec 31, 2006
  25. Move commit reencoding parameter parsing to revision.cJunio C Hamano, Dec 30, 2006
  26. Johannes SchindelinDec 31, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.