From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2016, #06; Thu, 21)
Date: Fri, 22 Apr 2016 14:38:45 -0400 [thread overview]
Message-ID: <20160422183844.GB7595@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqa8klr21p.fsf@gitster.mtv.corp.google.com>
On Fri, Apr 22, 2016 at 10:22:42AM -0700, Junio C Hamano wrote:
> >> * jk/push-client-deadlock-fix (2016-04-20) 5 commits
> [...]
> Thanks. Something like this, perhaps?
>
> "git push" from a corrupt repository that attempts to push a large
> number of refs deadlocked; the thread to relay rejection notices
> for these ref updates blocked on writing them to the main thread,
> after the main thread at the receiving end notices that the push
> failed and decides not to read these notices and return a failure.
Yep, that's perfect.
> >> * da/user-useconfigonly (2016-04-01) 2 commits
> [...]
> What often happens is that I start waiting, and then when
> necessary actions to move things forward is never taken, and there
> are many other topics that need my attention to move forward, I stop
> caring, especially when the topic is not something other people care
> about (if the original author does not care deeply enough, why
> should we?).
>
> Let me read it over again as it has been a while and then move it
> forward with your Reviewed-by's.
It is a minor bugfix, but I think worth doing. Adding reviewed-by me is
definitely fine.
-Peff
next prev parent reply other threads:[~2016-04-22 18:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 22:20 What's cooking in git.git (Apr 2016, #06; Thu, 21) Junio C Hamano
2016-04-21 22:32 ` Stefan Beller
2016-04-21 22:48 ` Pranit Bauva
2016-04-22 17:23 ` Junio C Hamano
2016-04-22 22:12 ` Junio C Hamano
2016-04-23 18:42 ` Pranit Bauva
2016-04-21 22:51 ` Santiago Torres
2016-04-21 23:20 ` Junio C Hamano
2016-04-22 4:42 ` Jeff King
2016-04-22 17:22 ` Junio C Hamano
2016-04-22 18:38 ` Jeff King [this message]
2016-04-22 5:01 ` Torsten Bögershausen
2016-04-22 17:23 ` Junio C Hamano
2016-04-22 14:04 ` Johannes Schindelin
2016-04-22 17:24 ` 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=20160422183844.GB7595@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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).