mtn --db=YOUR_DATABASE_DIRECTORY/ctwm.mtn \ db init
mtn --db=YOUR_DATABASE_DIRECTORYI/ctwm.mtn \ pull guardian.lp.se free.lp.se:X.ctwm
mtn --db=YOUR_DATABASE_DIRECTORY/ctwm.mtn --branch=free.lp.se:X.ctwm \ co CTWM_WORK_DIRECTORY
If you want write access, you have to create a key pair with your email address as identity, then extract the public half and send it to me.
mtn --db=YOUR_DATABASE_DIRECTORY/ctwm.mtn \ genkey your.mail@address.com
mtn --db=YOUR_DATABASE_DIRECTORY/ctwm.mtn \ pubkey your.mail@address.com > public_your.mail@address.com
When standing in the working directory, the database is recorded in MT/options, and the database itself contains data about the default server and collection to use (this got initialised by the first mtn ull), so further updates are done like this:
mtn pull
mtn update
When you have write access, these are practical operations.
mtn add FILE
monodone drop FILE
mtn rename -e OLDFILE NEWFILE
This variant only shows which files have changed, been added, deleted or renamed. This differs from cvs status, which shows the status of unknown files.
mtn status
mtn automate inventory
mtn commit [--message="message"]
mtn commit [--message="message"] FILE1 FILE2 ...
mtn push