Re: Push not writing to standard error

From: Chase Brammer <cbrammer@gmail.com>
Date: Oct 12, 2010, 22:18 UTC
Message-ID: <AANLkTikVE_iQ8nMdq7_G9aX17M3hQ4vM=oe2o=qynR-U@mail.gmail.com>
In-Reply-To: <20101012204845.GA12790@sigill.intra.peff.net>

Peff

Thanks for all the help. It worked fantastic. I hope you don't mind me packing this into a commit and submitting it to Junio. It is something I really need in the next release. I don't know much about protocol here, and I don't want to step on toes.

Chase

On Tue, Oct 12, 2010 at 2:48 PM, Jeff King <peff@peff.net> wrote:

Show 21 quoted lines

> On Tue, Oct 12, 2010 at 02:37:50PM -0600, Chase Brammer wrote:
>
>> Wow, I am amazed at how quick you churned that out.  I haven't
>> participated in the git patch and release cycle, so forgive my
>> ignorance.  Do you think that this will be released in the next
>> release (1.7.3.2) ? If so, any expectations on release date?
>
> Well, at 5 minutes it was really only 1 line of code per minute. ;)
>
> I'm hoping that somebody else on the list who has worked in the
> transport code recently can comment on whether this is the right fix.
> Did you test it? Does it fix your issue?
>
> If it seems OK, then somebody needs to submit a cleaned-up version with
> commit message to Junio, who will probably cook it in "next" for at
> least a few weeks, and then hopefully it would be in v1.7.3.2. He does
> maintenance releases as-needed, which seems to generally be every few
> weeks.
>
> -Peff
>