In message <87d61qhmw5.fsf@xxxxxxxxxxxxxxxxxxxx> on Mon, 16 Aug 2004 21:02:34
+0100, Bruce Stephens <monotone@xxxxxxxxxxxxxxxxxxxx> said:
monotone> Firstly there's the optional file arguments to revert. It's
monotone> not at all surprising that they're there---it's such a
monotone> natural thing to have, but it doesn't seem to be in the
monotone> documentation.
I just took the liberty to expand on this:
--- monotone.texi
+++ monotone.texi
@@ -3289,13 +3289,18 @@
@item monotone revert
-This command changes your working copy, so that changes you have made
-since the last checkout or update are discarded. It does this by
-changing every file listed in @file{MT/manifest} to have contents
-equal to the @sc{sha1} value listed in the manifest, and by erasing the
-@file{MT/work} file.
+@itemx monotone revert @var{filename...}
+With no files given, this command changes your working copy, so that
+changes you have made since the last checkout or update are discarded.
+It does this by changing every file listed in @file{MT/manifest} to
+have contents equal to the @sc{sha1} value listed in the manifest, and
+by erasing the @file{MT/work} file.
+If files are given as arguments, only those files are affected instead
+of the entirety of your working copy.
+
+
@item monotone update
This command incorporates ``recent'' changes found in your database
into your working copy. It does this by performing 3 separate
-----
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.
--
Richard Levitte richard@xxxxxxxxxxx
http://richard.levitte.org/
|
