Re: [Monotone-devel] viewmtn status

[Brian May]

On 14 December 2010 20:37, Thomas Moschny <address@hidden> wrote:
> the development version [1] should support the stdio format from
> monotone 0.46 and later.

Ok, good.

> [1] mtn clone
> 'mtn://code.monotone.ca/contrib?net.venge.monotone.viewmtn'

Errr... How do I do that? I am not familiar with this clone command.


address@hidden:/home/viewmtn# mtn clone
'mtn://code.monotone.ca/contrib?net.venge.monotone.viewmtn'
Usage: mtn [OPTION...] command [ARG...]

Options specific to 'mtn clone' (run 'mtn help' to see global options):

  --max-netsync-version <arg>  cause monotone to lie about the maximum
netsync protocol version that it
                               supports, mostly for debugging
  --min-netsync-version <arg>  cause monotone to lie about the minimum
netsync protocol version it
                               supports, useful for debugging or if
you want to prevent use of older
                               protocol versions
  --revision [ -r ] <arg>      select revision id for operation

Syntax specific to 'mtn clone':

  clone ADDRESS[:PORTNUMBER] BRANCH [DIRECTORY]

Description for 'mtn clone':

  Checks out a revision from a remote database into a directory.

  If a revision is given, that's the one that will be checked out.
Otherwise, it will be the head of the
  branch supplied.  If no directory is given, the branch name will be
used as directory


Have tried different variants, nothing seems to work for me. eg:

address@hidden:/home/viewmtn# mtn clone 'mtn://code.monotone.ca/contrib'
'net.venge.monotone.viewmtn'
mtn: doing anonymous pull; use -kKEYNAME if you need authentication
mtn: connecting to mtn://code.monotone.ca/contrib
mtn: network error: service name resolution failed for: mtn

-- 
Brian May <address@hidden>