monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-devel] [PATCH] mtn clone


From: William Uther
Subject: [Monotone-devel] [PATCH] mtn clone
Date: Sat, 24 Feb 2007 21:30:06 +1100

Hi all,

  Here's another patch.  This one implements mtn clone and some tests.

% ./mtn help clone
[snip]
Options specific to 'mtn clone':

  --branch [ -b ] <arg>    select branch cert for operation
  --exclude <arg>          leave out anything described by its argument
  --revision [ -r ] <arg>  select revision id for operation

     clone ADDRESS[:PORTNUMBER] [DIRECTORY]
       check out a revision from remote database into directory.
       If a revision is given, that's the one that will be checked out.
       Otherwise, it will be the head of the branch supplied.
If no directory is given, the branch name will be used as directory


You can specify --db and it will use that DB rather than making a new one. It currently uses pull internally, so will do anonymous pull unless you use -k.

Issues:
- You must specify a --branch option. Should I move that to a non- option argument? - The db is stored as _MTN/mtn.db. It is stored in _MTN/options as an absolute path, so if you move the working copy, it'll lose track of the db. - It doesn't clean up in some failure situations. I made it fail if the destination dir exists, so it is just a matter of catching any failures and removing the directory. I thought I'd post this much first.

Be well,

Will          :-}

Attachment: mtn_clone.patch
Description: Binary data




reply via email to

[Prev in Thread] Current Thread [Next in Thread]