All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>,
	git@vger.kernel.org, Erik Faye-Lund <kusmabite@gmail.com>,
	Aman Gupta <aman@github.com>, Ryan Tomayko <ryan@github.com>
Subject: Re: [1.7.2] Please cherry-pick "upload-pack: start pack-objects before async rev-list"
Date: Thu, 26 May 2011 12:11:10 -0500	[thread overview]
Message-ID: <20110526171110.GE24931@elie> (raw)
In-Reply-To: <7voc2pxutw.fsf@alter.siamese.dyndns.org>

Junio C Hamano wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:

>> This server-side deadlock started being triggered by shallow clones
>> when sv.gnu.org upgraded to v1.7.2.5 a couple of months ago[1].  So it
>> might be worth thinking about how to help upgrade-averse server admins
>> to fix it.
>
> Upgrade-averse people can be fixed by keeping them closer to the tip, no?
> I don't plan to issue any more maintenance release on 1.7.2.X track beyond
> what is already released, unless there is a high priority security fix or
> something.
>
> Placing it on 1.7.4.X and newer maintenance tracks is a separate matter.

Ok, that's fine with me.  (To be clear, I was suggesting
cherry-picking to the branches but not making a release, though I
realize that would mean more time wasted the next time it is time to
make a high priority security fix.)

I'll cherry-pick it as a Debian-specific patch, which should be good
enough to get shallow clones working again on the affected servers.

      reply	other threads:[~2011-05-26 17:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  5:36 [RFC] upload-pack deadlock Jeff King
2011-04-06 17:20 ` Junio C Hamano
2011-04-06 17:54   ` Jeff King
2011-04-06 19:15     ` Erik Faye-Lund
2011-04-06 21:38       ` Jeff King
2011-04-06 21:33     ` Jeff King
2011-04-18  5:34       ` Jonathan Nieder
2011-05-26  6:45       ` [1.7.2] Please cherry-pick "upload-pack: start pack-objects before async rev-list" Jonathan Nieder
2011-05-26 16:58         ` Junio C Hamano
2011-05-26 17:11           ` Jonathan Nieder [this message]

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=20110526171110.GE24931@elie \
    --to=jrnieder@gmail.com \
    --cc=aman@github.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kusmabite@gmail.com \
    --cc=peff@peff.net \
    --cc=ryan@github.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.