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

Re: kompare won't parse git diffs

From
Junio C Hamano <junkio@cox.net>
Date
Aug 2, 2006, 19:17 UTC
Message-ID
<7vy7u7t0ap.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<eaqpt2$ots$1@sea.gmane.org>
Jakub Narebski <jnareb@gmail.com> writes:
Show 7 quoted lines
>> Not only is the git patch format perfectly standard and accepted by other 
>> tools, it's much better designed than the brain-damaged syntax that GNU 
>> patch uses (which adds a tab and a timestamp after the filenames). In 
>> particular, with git patches it is easy to get filenames that have spaces 
>> and tabs in them right. 
>
> What about filenames with end-of-line character in them? Is it quoted?

You could have done a bit of homework yourself to find that out easily ;-). Anyway, the answer is yes.

	http://marc.theaimsgroup.com/?l=git&m=112927316408690

I wonder what happened to the plan to update GNU diff/patch to also emit/understand the c-style quoted paths. Paul?

Previous: Jakub NarebskiNext: Paul Eggert
Message 4 of 9 in “kompare won't parse git diffs”
  1. Andy ParkinsAug 2, 2006
  2. Linus TorvaldsAug 2, 2006
  3. Jakub NarebskiAug 2, 2006
  4. Junio C HamanoAug 2, 2006
  5. Paul EggertAug 6, 2006
  6. Linus TorvaldsAug 2, 2006
  7. Jakub NarebskiAug 2, 2006
  8. Linus TorvaldsAug 2, 2006
  9. Andy ParkinsAug 2, 2006

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.