git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Grimm <koreth@midwinter.com>
To: Jan Hudec <bulb@ucw.cz>
Cc: Robert Boone <robert@rlb3.com>, git@vger.kernel.org
Subject: Re: Centralized processes in git
Date: Tue, 21 Aug 2007 08:40:37 +0800	[thread overview]
Message-ID: <46CA3485.4080207@midwinter.com> (raw)
In-Reply-To: <46CA3398.9060803@midwinter.com>

Steven Grimm wrote:
> the repository-altering commands would grab a shared lock.

I guess that's a bit confusing -- what I mean to say is that the 
repository-altering commands that today do not lock the repository would 
grab a shared lock such that, in the absence of something else grabbing 
the exclusive lock, they will continue to effectively not lock the 
repository. IOW, by grabbing the shared lock they will continue to 
exhibit their current behavior under normal conditions.

-Steve

  reply	other threads:[~2007-08-21  0:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 18:30 Centralized processes in git Robert Boone
2007-08-20 19:29 ` Jan Hudec
2007-08-21  0:36   ` Steven Grimm
2007-08-21  0:40     ` Steven Grimm [this message]
2007-08-21  6:13     ` Jeff King

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=46CA3485.4080207@midwinter.com \
    --to=koreth@midwinter.com \
    --cc=bulb@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=robert@rlb3.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).