Am 17.11.2005 um 20:03 schrieb Juliusz Chroboczek:
Here's an outline of what could be done, taking record as an example.
Add three new (sub)commands:
darcs batch take-lock
darcs batch release-lock
darcs batch whatsnew
darcs batch record
The locking commands should be self-explanatory. Batch whatsnew would
give a numbered list of hunks, in an easy to parse format.
Batch record is like record, but it doesn't take a lock (assumed to
already have been taken by an explicit take-lock), and instead of
being interactive, takes a subset of the hunk indices produced by
batch whatsnew.
FYI, here is what BitKeeper's man page says:
SYNOPSIS
bk lock [-l|r|w|L|U] [-q] [directory]
DESCRIPTION
The lock command can be used to lock an entire reposi-
tory or to list the lockers of a repository. If a
directory is specified, the operation applies to the
repository rooted at that directory.
Since a lock is valid only as long as the locking
process exists, when placing lock, the lock command
does not exit, it goes to sleep waiting for a signal.
OPTIONS
-l List the lockers of a repository.
-q quiet, exit status only
-r Add a read lock (non-exclusive).
-w Add a write lock (exclusive).
-L Wait for the repository to become locked (primar-
ily used for testing).
-U Wait for the repository to become unlocked (pri-
marily used for testing).
EXIT STATUS
If called with no options or if called with the -l
option, lock exits 1 if the repository has locks and
exits 0 if the repository has no locks.
If called with either -r or -w, lock exits 1 if unable
to lock the repository.
SEE ALSO
bk help unlock
CATEGORY
Repository
BitMover, Inc 2002/09/17 bk lock(1)
Daniel
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
