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

Re: [PATCH] Allow curl to rewind the read buffers

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 1, 2009, 16:19 UTC
Message-ID
<7vbprg1h3m.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<Pine.LNX.4.64.0904011809080.5901@localhost.localdomain>
Martin Storsjö <martin@martin.st> writes:
> Rewinding of the read buffers may be needed when doing HTTP PUT or POST
> (or PROPFIND) with multi-pass authentication methods.

It may be obvious to people proficient in cURL, but I had to guess that you perhaps meant to say "when using multi-pass authentication methods, cURL library may need to rewind the read buffers (depending on what is fed by the server), and in order to allow the library to do so, we need to tell it how by providing the way to manipulate the buffers we supply with these IOCTL callbacks."

Do I understand you correctly?

My point is that the your two-line statement of fact (with a bit more explanation of the fact that follows) was clear but it was unclear to me how that fact translates to the need of what the patch does. We would want the commit log message to be helpful to people who look at the code 6 months down the line and wonder why these lines were added.

Please do not make me guess. I won't claim that other people would be even less clueful than I am, but I am reasonably sure that more than half of the people who read this patch would share my uneasiness of not clearly reading how your statement of fact leads to your conclusion.

Thanks.
Previous: Martin StorsjöNext: Martin Storsjö
Message 2 of 5 in “Allow curl to rewind the read buffers”
  1. Allow curl to rewind the read buffersMartin Storsjö, Apr 1, 2009
  2. Junio C HamanoApr 1, 2009
  3. Martin StorsjöApr 1, 2009
  4. Allow curl to rewind the read buffersMartin Storsjö, Apr 1, 2009
  5. Junio C HamanoApr 2, 2009

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.