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

Re: [PATCH 2/3] tests: Test how well "git apply" copes with weird filenames

From
Andreas Schwab <schwab@linux-m68k.org>
Date
Jul 24, 2010, 08:03 UTC
Message-ID
<m2r5iti9w0.fsf@igel.home>
In-Reply-To
<20100724011114.GC13670@burratino>
Jonathan Nieder <jrnieder@gmail.com> writes:
> The tests assume a reasonably well-behaved “diff -u” and “pr”
> to produce the (possibly whitespace-damaged) patches.  On platforms
> without those commands, skip the tests.
pr -T is not portable.  What's wrong with expand?
Andreas.
-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Previous: Jonathan NiederNext: Jonathan Nieder
Message 4 of 6 in “apply: handle traditional patches with spaces in filename”
  1. 0/3 apply: handle traditional patches with spaces in filenameJonathan Nieder, Jul 24, 2010
  2. 1/3 apply: Split quoted filename handling into new functionJonathan Nieder, Jul 24, 2010
  3. 2/3 tests: Test how well "git apply" copes with weird filenamesJonathan Nieder, Jul 24, 2010
  4. Andreas SchwabJul 24, 2010
  5. Jonathan NiederJul 24, 2010
  6. 3/3 apply: Handle traditional patches with space in filenameJonathan Nieder, Jul 24, 2010

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.