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

Re: [PATCH] Make git-archimport log entries more consistent

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 30, 2007, 03:14 UTC
Message-ID
<7vmyw9af3q.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<617indss2f.fsf@fencepost.gnu.org>
Miles Bader <miles@gnu.org> writes:
Show 8 quoted lines
> When appending the "git-archimport-id:" line to the end of log entries,
> git-archimport would use two blank lines as a separator when there was no
> body in the arch log (only a Summary: line), and zero blank lines when there
> was a body (making it hard to see the break between the actual log message
> and the git-archimport-id: line).
>
> This patch makes git-archimport generate one blank line as a separator in all
> cases.

I would not have any problem with what the result of this patch would record in the commits, if it was what it did from the very beginning. But this is a change in behaviour; I'd like to know if people who use archimport _rely_ on the current behaviour...

Anybody?
Previous: Miles BaderNext: Miles Bader
Message 2 of 6 in “Make git-archimport log entries more consistent”
  1. Make git-archimport log entries more consistentMiles Bader, Aug 30, 2007
  2. Junio C HamanoAug 30, 2007
  3. Miles BaderAug 30, 2007
  4. Junio C HamanoAug 30, 2007
  5. David KastrupAug 30, 2007
  6. Junio C HamanoAug 30, 2007

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.