All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Martin Storsj? <martin@martin.st>, Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, rctay89@gmail.com
Subject: Re: What's cooking in git.git (Dec 2009, #02; Sat, 05)
Date: Mon, 7 Dec 2009 07:37:36 -0800	[thread overview]
Message-ID: <20091207153736.GC17173@spearce.org> (raw)
In-Reply-To: <alpine.DEB.2.00.0912061738580.5582@cone.home.martin.st>

Martin Storsj? <martin@martin.st> wrote:
> On Sun, 6 Dec 2009, Junio C Hamano wrote:
> > 
> > * tr/http-updates (2009-12-01) 3 commits
> >  - Allow curl to rewind the RPC read buffer
> >  - Add an option for using any HTTP authentication scheme, not only basic
> >  - http: maintain curl sessions
> > 
> > There was a discussion on a better structure not to require rewinding in
> > the first place?  I didn't follow it closely...
> 
> I think the conclusion is: Rewinding support isn't strictly necessary, 
> there's a number of mechanisms in both git and curl that should make sure 
> that those cases shouldn't surface. A few of them in curl have an 
> unfortunate conincidence of bugs up until the latest version, though, 
> leaving much fewer mechanisms in place to avoid this.
> 
> Since that patch is quite non-intrusive I think it's a good safeguard, 
> though. What do you think, Tay, keep it or leave it?

I think the conclusion of the thread was that what you have queued
in tr/http-updates is OK as-is.  The patch to grow the postbuffer
to store the entire request wasn't a good idea and got dropped.

-- 
Shawn.

  reply	other threads:[~2009-12-07 15:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-06  8:17 What's cooking in git.git (Dec 2009, #02; Sat, 05) Junio C Hamano
2009-12-06 15:59 ` Martin Storsjö
2009-12-07 15:37   ` Shawn O. Pearce [this message]
2009-12-07 20:07     ` Junio C Hamano
2009-12-08  5:58     ` Tay Ray Chuan

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=20091207153736.GC17173@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=martin@martin.st \
    --cc=rctay89@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.