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

Re: [BUG] gitweb on repo.or.cz shows buggy commitdiff

From
Jakub Narebski <jnareb@gmail.com>
Date
Aug 27, 2007, 01:12 UTC
Message-ID
<200708270312.18905.jnareb@gmail.com>
In-Reply-To
<20070827004838.GO1219@pasky.or.cz>
Petr Baudis wrote:
> On Mon, Aug 27, 2007 at 02:30:04AM CEST, Jakub Narebski wrote:
>> 2. Alternate solution is to note that we have split patch only in the case
>> of 'T' (type change) status, and for typechange we always split patch in
>> two, so there are two patches corresponding to single raw diff-tree line.
[...]
> 
> I'd prefer this solution, though I think split patch could also happen
> if you use -B (which I think is very good idea to use and it's a pity
> that it isn't default - or is it?).

No, 'B' status does not means split patch: it only affects how the patchset looks like, i.e first delete all then add all, instead of doing change chunk by chunk.

Or I think it does. "git log --raw -p --diff-filter=B -B origin" on git.git repository returns rather strange results for the difftree part...

-- 
Jakub Narebski
Poland
Previous: Petr Baudis
Message 5 of 5 in “[BUG] gitweb on repo.or.cz shows buggy commitdiff”
  1. Yann DirsonJul 29, 2007
  2. Petr BaudisAug 25, 2007
  3. Jakub NarebskiAug 27, 2007
  4. Petr BaudisAug 27, 2007
  5. Jakub NarebskiAug 27, 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.