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, 21:46 UTC
Message-ID
<7v3ay08zli.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<86myw9jwga.fsf@lola.quinscape.zz>
David Kastrup <dak@gnu.org> writes:
> ... but given that the previous format was
> not declared canonical at any point of time, the question is whether
> anyone will indeed notice before things break.

I tend to agree with you. archimport is so specialized that if you are not using it you would not care, and small population who are using it and relying on the old behaviour would notice breakaage right away, so "Let's see who screams" sounds like the right thing to do.

Previous: David Kastrup
Message 6 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.