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

Re: [PATCH] gitweb: Fix and simplify "split patch" detection

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 3, 2007, 11:00 UTC
Message-ID
<7vtzqcj9ni.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<200709031147.32910.jnareb@gmail.com>
Jakub Narebski <jnareb@gmail.com> writes:
> I wonder if the post-image name is unique in raw format of diff
> output, and can be used alone to check if there are two patches
> per one raw output format line...
I think that is a very sane assumption.

You may have a situation that a single preimage is used to produce more than one postimage, but it does not make sense to say this postimage is produced by doing this to that preimage and there is another way to produce the same postimage using something else.

At least, I do not think the diffcore chain is _capable_ of coming up with such alternatives even if it wanted to ;-).

Previous: Jakub Narebski
Message 4 of 4 in “gitweb: Fix and simplify "split patch" detection”
  1. gitweb: Fix and simplify "split patch" detectionJakub Narebski, Sep 2, 2007
  2. Junio C HamanoSep 3, 2007
  3. Jakub NarebskiSep 3, 2007
  4. Junio C HamanoSep 3, 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.