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

Re: [PATCH] http-push: trim trailing newline from remote symref

From
Jeff King <peff@peff.net>
Date
Jan 13, 2015, 19:58 UTC
Message-ID
<20150113195806.GA13282@peff.net>
In-Reply-To
<4E1001F7-2D26-483A-9339-E2570559ECF0@gmail.com>
On Tue, Jan 13, 2015 at 08:26:31AM -0800, Kyle J. McKay wrote:
Show 6 quoted lines
> I have this line in my 2.1.4 test output log:
> 
> t5540-http-push-webdav.sh .......................... ok
> [...]
> I do not build with NO_EXPAT.  This is running the tests on OS X without
> this patch applied.  Is something else required to get a failure?
Hmm. I think it is probably this:
  http://curl.haxx.se/docs/adv_20150108B.html

where curl has started complaining about URLs with newlines in them. So ae021d8 did introduce a bug, but older versions of curl did not really care. The combination of ae021d8 with a new version of curl triggers the problem.

And that also explains why it worked prior to eecc8367f4; curl was more forgiving. Also, interestingly, if you "git log -S'- 6' http-push.c", you can see the exact same bug reappear and go away in 2006/2007. The implicit "chop one character" behavior is there in the original 3dfaf7bc, adding http-push support. Then it disappears as a side effect of bfbd0bb6, and then comes back again in eecc8367.

Anyway. I think my patch is still the right thing. But that does explain why we didn't notice the test failure.

-Peff
Previous: Kyle J. McKayNext: Kyle J. McKay
Message 3 of 6 in “http-push: trim trailing newline from remote symref”
  1. http-push: trim trailing newline from remote symrefJeff King, Jan 13, 2015
  2. Kyle J. McKayJan 13, 2015
  3. Jeff KingJan 13, 2015
  4. Kyle J. McKayJan 14, 2015
  5. Junio C HamanoJan 16, 2015
  6. Jeff KingJan 13, 2015

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.