[Monotone-devel] Inconsistent behaviour and others: clone vs. pull

[Dennis Schridde]

Hello!

(1)
I noticed an inconsistent behaviour between clone and pull:
clone by default uses a key to connect to the host, while pull does not.

$ mtn clone -b net.venge.monotone.trac-plugin monotone.ca tracmtn
mtn: setting default server to monotone.ca
mtn: setting default branch include pattern 
to 'net.venge.monotone.trac\-plugin'
mtn: setting default branch exclude pattern to ''
enter passphrase for key ID [mykey]:
mtn: connecting to monotone.ca

$ mtn --db=fuubar.mtn pull monotone.ca "net.venge.monotone.trac-plugin*"
mtn: setting default server to monotone.ca
mtn: setting default branch include pattern 
to 'net.venge.monotone.trac\-plugin*'
mtn: setting default branch exclude pattern to ''
mtn: doing anonymous pull; use -kKEYNAME if you need authentication
mtn: connecting to monotone.ca


(2)
The fact that the server does not know they I try to authenticate with is 
denote with this cryptic message:
mtn: warning: protocol error while processing peer monotone.ca: 'received 
network error: remote public key 
hash '9625eeea718bd974563ddedde9ff00e3195449a9' is unknown'


(3)
clone takes a -b argument to specify the branch, while pull wants it as a 
normal argument.


(4)
There doesnt seem to be an obvious way to make clone connect anonymously.


--Dennis

signature.asc
Description: This is a digitally signed message part.