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

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

From
Miles Bader <miles@gnu.org>
Date
Aug 30, 2007, 03:19 UTC
Message-ID
<fc339e4a0708292019s3d4f6914h4f9efe6f1172c380@mail.gmail.com>
In-Reply-To
<7vmyw9af3q.fsf@gitster.siamese.dyndns.org>
On 8/30/07, Junio C Hamano <gitster@pobox.com> wrote:
Show 7 quoted lines
> > 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...

Good point, though it seems pretty unlikely -- the most notable thing about the old behavior was that the results were inconsistent... :-)

-Miles
-- 
Do not taunt Happy Fun Ball.
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 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.