From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: git <git@vger.kernel.org>
Subject: Interest in locking mechanism?
Date: Tue, 12 Jan 2010 13:10:10 -0500 [thread overview]
Message-ID: <1263319565-sup-1767@ezyang> (raw)
I have a few friends that still use RCS for their version control
needs. We have argued over various points between RCS and Git, and
as far as I can tell the one thing RCS has that Git does not is
a locking mechanism. That is to say, co -l checks out a file and
also gives you a lock on it, preventing others from futzing with it,
and ci -u checks in the file and releases your lock. This is
useful if you have a shared working copy on a multiuser system or
on a network file system, and you don't want conflicts.
I was wondering if there would be interest in such a feature on
the Git developers side.
Cheers,
Edward
next reply other threads:[~2010-01-12 18:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 18:10 Edward Z. Yang [this message]
2010-01-12 18:29 ` Interest in locking mechanism? B Smith-Mannschott
2010-01-12 18:33 ` Edward Z. Yang
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=1263319565-sup-1767@ezyang \
--to=ezyang@mit.edu \
--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).