monotone

monotone Mtn Source Tree

Root/debian/monotone.1

1.TH "monotone" 1
2.SH NAME
3monotone \- distributed version control system
4.SH SYNOPSIS
5\fBmonotone\fP \fI[options] <command> [parameters]\fP
6.P
7Options, which affect global behavior or set default values, come
8first in the argument list. A single command must follow, indicating
9the operation to perform, followed by parameters which vary depending
10on the command.
11.SS Note
12This manpage is a summary of some of the features and commands of
13\fBmonotone\fP, but it is not the most detailed source of information
14available. For a complete discussion of the concepts and a tutorial on
15its use, please refer to the texinfo manual (via the \fBinfo
16monotone\fP command, or online).
17.SS Commands
18.TP
19\fBcomment\fP \fI(file|manifest) <id>\fP
20Write a comment cert for a file or manifest version.
21.TP
22\fBapprove\fP \fI(file|manifest) <id>\fP
23Make a cert approving of a file or manifest version.
24.TP
25\fBdisapprove\fP \fI(file|manifest) <id>\fP
26Make a cert disapproving of a file or manifest version.
27.TP
28\fBtag\fP \fI<id> <tagname>\fP
29Put a symbolic tag cert on a manifest version.
30.TP
31\fBagraph\fP
32Dump ancestry graph to stdout.
33.TP
34\fBdiff\fP
35Show diffs between working copy and database.
36.TP
37\fBstatus\fP
38Show status of working copy.
39.TP
40\fBcert\fP \fI(file|manifest) <id> <certname> [certval]\fP
41Create a custom cert for a file or manifest. Reads cert value
42from stdin if no value given on command line.
43.TP
44\fBgenkey\fP \fI<keyid>\fP
45Generate an RSA key-pair and store it in the database.
46.TP
47\fBlscerts\fP \fI(file|manifest) <id>\fP
48List certs associated with manifest or file.
49.TP
50\fBlskeys\fP \fI[partial-id]\fP
51List keys matching glob, or list all keys if no glob given.
52.TP
53\fBfetch\fP \fI[URL] [groupname]\fP
54Fetch recent packets from network servers. Does not read public
55or private key packets; use the \fBread\fP command instead.
56.TP
57\fBpost\fP
58Post queued packets to network servers.
59.TP
60\fBfcerts\fP \fI<id>\fP
61Write file cert packets to stdout.
62.TP
63\fBfdata\fP \fI<id>\fP
64Write file data packet to stdout.
65.TP
66\fBfdelta\fP \fI<oldid> <newid>\fP
67Write file delta packet to stdout.
68.TP
69\fBmcerts\fP \fI<id>\fP
70Write manifest cert packets to stdout.
71.TP
72\fBmdata\fP \fI<id>\fP
73Write manifest data packet to stdout.
74.TP
75\fBprivkey\fP \fI<id>\fP
76Write private key packet to stdout.
77.TP
78\fBpubkey\fP \fI<id>\fP
79Write public key packet to stdout.
80.TP
81\fBread\fP
82Read packets from stdin. This is the only way of reading cryptographic
83key packets; the \fBfetch\fP command will not read public or private
84keys from the network. It is very important to \fBonly read keys from
85trusted sources\fP; all other trust relationships are built out of the
86trust assigned to keys.
87.TP
88\fBcvs_import\fP \fI<cvsroot>\fP
89import all versions in CVS repository
90.TP
91\fBrcs_import\fP \fI<rcsfile> ...\fP
92import all versions in RCS files
93.TP
94\fBcheckout\fP \fI<manifest-id>\fP
95Check out tree state from database.
96.TP
97\fBcat\fP \fI(file|manifest) <id>\fP
98Write file or manifest from database to stdout.
99.TP
100\fBheads\fP
101Show unmerged heads of branch, or report when branch is merged.
102.TP
103\fBmerge\fP
104Merge unmerged heads of branch.
105.TP
106\fBadd\fP \fI<pathname> [...]\fP
107Add files to working copy. adding a file does not copy it into the database,
108merely adds it to the manifest. You must \fBcommit\fP your changes in order
109to copy added files to the database.
110.TP
111\fBcommit\fP \fI[log message]\fP
112Commit working copy to database. If a log message is provided on the command
113line, it is used; otherwise a log message editor will be invoked.
114.TP
115\fBdrop\fP \fI<pathname> [...]\fP
116Drop files from working copy. Files are not deleted from working copy,
117merely removed from the manifest.
118.TP
119\fBupdate\fP \fI[sort keys...]\fP
120Update working copy, relative to sorting keys.
121.SH DESCRIPTION
122Monotone is a version control system, which allows you to keep old
123versions of files, as well as special \fImanifest files\fP which
124describe the location of files in a tree. Unlike other systems,
125versions in monotone are \fIidentified\fP by cryptographic hash, and
126operations are authenticated by individual users' evaluating
127cryptographic signatures on meta-data, rather than any central
128authority.
129
130Monotone keeps a collection of versions in a single-file relational
131database. It is essentially serverless, using network servers only as
132untrusted communication facilities. A monotone database is a regular
133file, which contains all the information needed to extract previous
134versions of files, verify signatures, merge and modify versions, and
135communicate with network servers.
136.SH OPTIONS
137.TP
138\fB--help\fP
139Print help message.
140.TP
141\fB--verbose\fP
142Trace execution verbosely. default is to be silent, unless
143an error occurs, in which case failure log is dumped.
144.TP
145\fB--nostd\fP
146Do not evaluate "standard" lua hooks compiled into \fBmonotone\fP.
147.TP
148\fB--norc\fP
149Do not load lua hooks from user's \fB~/.monotonerc\fP file.
150.TP
151\fB--rcfile=\fP\fI<file>\fP
152Load extra lua hooks from \fIfile\fP (may be given multiple times).
153.TP
154\fB--db=\fP\fI<file>\fP
155Use database in \fIfile\fP. default is \fBmonotone.db\fP.
156.TP
157\fB--key=\fP\fI<keyid>\fP
158Use \fIkeyid\fP for operations which produce RSA signatures. Default
159is inferred from presence of unique private key in database. Can also
160be set with environment variable \fBMT_KEY\fP or customized on a per-branch
161basis with hook function \fBget_branch_key(branchname)\fP.
162.TP
163\fB--branch=\fP\fI<branchname>\fP
164Use \fIbranchname\fP for operations on a branch. Default is inferred
165in operations on existing branches (commit, update, etc). Can also be set
166with environment variable \fBMT_BRANCH\fP.
167.SH ENVIRONMENT
168.TP
169\fBMT_DB\fP
170Database file to use
171(same as \fB--db\fP option).
172.TP
173\fBMT_KEY\fP
174Key to use for operations which produce RSA signatures
175(same as \fB--key\fP option).
176.TP
177\fBMT_BRANCH\fP
178Branch name to use for operations on a branch
179(same as --branch option).
180.TP
181\fBEDITOR\fP
182Used to edit comments, log messages, etc.
183.TP
184\fBVISUAL\fP
185Used in preference to \fBEDITOR\fP, if set.
186.SH FILES
187.TP
188\fB$HOME/.monotonerc\fP
189A lua script, used as a customization file.
190.SH NOTES
191.IP \(bu
192Command line options override environment variables.
193.IP \(bu
194Settings in lua scripts (such as \fB.monotonerc\fP)
195override command line options and environment variables.
196.SH "SEE ALSO"
197\fBinfo monotone\fP
198.SH BUGS
199None known, please report any found.
200.SH AUTHOR
201graydon hoare <graydon@pobox.com>

Archive Download this file

Branches

Tags

Quick Links:     www.monotone.ca    -     Downloads    -     Documentation    -     Wiki    -     Code Forge    -     Build Status