> > mtn sync mtn://server/foobar > > ... huh? In every other networkable SCM today, scm://server/name URIs can be used in straightforward ways with a single server host to select entirely separate databases (with distinct local auth controls) based what "name" the client specified.
AIUI, the usher commands in the netsync protocol send the whole original command line string (here "mtn://server/foobar") to the server, so usher can use that however it likes to disambiguate what database to talk to. The fix that allows "mtn://server" to work also allows "mtn://server/name" so that the rest of the story can be done quite nicely just with more minor hacking on usher. > Is it possible you could write a test case or two for this bug? The test is any push/pull/sync operation using "mtn://server" instead of "server" (or "mtn://server:port/" instead of "server:port") as the ADDRESS parameter. Thanks, Roland _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
