Thread (8 messages) flat view 8 messages, 4 authors, 2016-06-15

Re: Push not writing to standard error

From: Chase Brammer <hidden>
Date: 2016-06-15 22:49:46

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 [off-list ref] wrote:
On Tue, Oct 12, 2010 at 02:37:50PM -0600, Chase Brammer wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help