From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: B Smith-Mannschott <bsmith.occs@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Interest in locking mechanism?
Date: Tue, 12 Jan 2010 13:33:49 -0500 [thread overview]
Message-ID: <1263321111-sup-4827@ezyang> (raw)
In-Reply-To: <28c656e21001121029h42544f3er6eedf8465851fec1@mail.gmail.com>
Excerpts from B Smith-Mannschott's message of Tue Jan 12 13:29:41 -0500 2010:
> How do you imagine that this would work in a distributed system such
> as git? What would it mean to have the lock for "a file", when each
> user effectively has their own branch?
Hi Ben,
Good question. I don't intend for the locking mechanism to leak into
the distributed model of Git. It is solely for working copies, which /are/
centralized (just there can be a lot of them), when multiple people might
be editing the same working copy.
There is a somewhat natural question of: well, you should clone, make your
changes in your own copy, and then push them back. That is arguably the
correct mechanism. However, for casual users batonning changes from one
repository to another is often more overhead than is really necessary, and
I think a working copy locking mechanism will help for simple cases.
Cheers,
Edward
next prev parent reply other threads:[~2010-01-12 18:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 18:10 Interest in locking mechanism? Edward Z. Yang
2010-01-12 18:29 ` B Smith-Mannschott
2010-01-12 18:33 ` Edward Z. Yang [this message]
2010-01-12 18:37 ` Tomas Carnecky
2010-01-12 19:01 ` Avery Pennarun
2010-01-12 19:11 ` Edward Z. Yang
2010-01-12 19:24 ` Avery Pennarun
2010-01-12 19:33 ` Martin Langhoff
2010-01-12 19:43 ` Edward Z. Yang
2010-01-12 20:25 ` Avery Pennarun
2010-01-12 19:26 ` Martin Langhoff
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=1263321111-sup-4827@ezyang \
--to=ezyang@mit.edu \
--cc=bsmith.occs@gmail.com \
--cc=git@vger.kernel.org \
/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).