Hendrik Boom wrote: > On http://wiki.monotone.ca/SelfHostingInfo/ it says:
> > $ # Command for monotone <=0.48 > $ mtn --db=mtn.db clone mtn://monotone.ca/monotone "?net.venge.monotone*" \ > -b net.venge.monotone monotone > > but when I try this I get: > > hend...@april:~/dv/mtn$ mtn --db=mtn.db clone mtn://monotone.ca/monotone > "?net.venge.monotone*" -b net.venge.monotone monotone > Usage: mtn [OPTION...] command [ARG...] [...] That's because of: Wed Sep 3 21:13:18 UTC 2008 0.41 release. Changes - 'mtn clone' now takes a branch argument rather than a branch option which is more what people expect given the fact that mtn push/pull/sync do not use a branch option either. Could someone please add the relevant information for monotone <= 0.40 in SelfHostingInfo? For that matter, there should also be an entry for monotone <= 0.33, since the "clone" command appeared in 0.34. And perhaps a note to the effect that monotone < 0.26 is no longer supported due to netsync compatibility being broken in 0.26. <rant> People do not necessarily use the latest and greatest version of anything, for various reasons. One possible reason is that Debian stable releases are supported for one year after the next stable release becomes available; this means the Debian 5.0 "Lenny" will be supported *at least* until November 2011 (in the unlikely event that Debian 6.0 "Squeeze" is released this month). There are other "long-term-support" distributions out there; Red Hat Enterprise Linux for example has a 7-year support policy (!). </rant> -- Ludovic Brenta. _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel