git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Martin Storsjö" <martin@martin.st>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Allow curl to rewind the read buffers
Date: Wed, 01 Apr 2009 09:19:57 -0700	[thread overview]
Message-ID: <7vbprg1h3m.fsf@gitster.siamese.dyndns.org> (raw)
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.

  reply	other threads:[~2009-04-01 16:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01 15:10 [PATCH] Allow curl to rewind the read buffers Martin Storsjö
2009-04-01 16:19 ` Junio C Hamano [this message]
2009-04-01 16:46   ` Martin Storsjö
2009-04-01 16:48   ` Martin Storsjö
2009-04-02  7:03     ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vbprg1h3m.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=martin@martin.st \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).