On Sun, Apr 12, 2009 at 03:20:41PM +0200, Markus Wanner wrote: > Hello Hendrik, > > Hendrik Boom wrote: > >>> With the command > >>> > >>> mtn cvs_import pathname > >>> > >>> does pathname need to be the name of a file or directory on the locel > >>> system, or is there come convention that allows mtn to use a remote cvs > >>> repository accessible over the network using, say, anonymous CVS login? > > Please see the fine manual: > > > Usage: mtn [OPTION...] command [ARG...] > > > > Options specific to 'mtn cvs_import' (run 'mtn help' to see global options): > > > > --branch [ -b ] <arg> select branch cert for operation > > > > Syntax specific to 'mtn cvs_import': > > > > cvs_import CVSROOT > > The CVSROOT is the directory on your CVS server. > > If that's not available, I've successfully used cvssuck, for example, > which mirrors the CVSROOT from a remote server. However, note that this > tool cannot mirror all of the original server's contents. >
It looks like I'll have to ask for a .tgz of the cvs repository. Thanks. > > The problem with cvs_import (and that applies to my branch as well) is, > that it currently doesn't support successive imports. Nor does it > provide any way to propagate back to your CVS server. And that stuff would be on the cvssync branch, right? Which particular cvssync subbranch should I be considering? (a) for use, or (b) to contribute towards testing it? -- hendrik _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
