Re: What's cooking in git.git (Nov 2015, #03; Fri, 20)

From: Jeff King <peff@peff.net>
Date: Nov 23, 2015, 18:57 UTC
Message-ID: <20151123185718.GB2597@sigill.intra.peff.net>
In-Reply-To: <alpine.DEB.1.00.1511231407380.1686@s15462909.onlinehome-server.info>

On Mon, Nov 23, 2015 at 02:09:42PM +0100, Johannes Schindelin wrote:

Show 17 quoted lines

> On Fri, 20 Nov 2015, Jeff King wrote:
> 
> > * pt/http-socks-proxy (2015-11-20) 1 commit
> >   (merged to 'next' on 2015-11-20 at dc6ae48)
> >  + remote-http(s): support SOCKS proxies
> > 
> >  Add support for talking http/https over socks proxy.
> > 
> >  Will cook in 'next'.
> 
> With all due respect, I do not thing this needs more cooking, as it
> 
> 1. was tested extensively by yours truly in the Git for Windows context,
>    and it
> 
> 2. cannot possibly break anything because it tests specifically for the
>    "socks:" prefix. It is a pure new feature.

Any time I want to say "cannot possibly" I start to get very worried that I have missed something. :)

I do think this topic looks OK, but it just made it into next during the last integration cycle (it was waiting on Pat's signoff, which I amended). I think it should be OK to cook in next for a few days and then merge to master (i.e., plenty of time for v2.7).

Thanks (and thank you for extra feedback; especially because of the maintainer switch I do not have full context on all of the topics).

-Peff