On Sun, May 14, 2006 at 11:28:49PM -0300, Jeronimo Pellegrini wrote: > On Sun, May 14, 2006 at 07:32:50PM -0500, Timothy Brownawell wrote: > > On Sun, 2006-05-14 at 21:05 -0300, Jeronimo Pellegrini wrote: > > > And how can I tell usher what key monoone should use? I suppose I should > > > have > > > only one key in ~/.monotone so I can use usher? > > > > Umm... pull the latest version and put > > monotone "mtn" "-k" "my_key" > > in the config file? (The -a and -l options are also moved to the config > > file now, as "listenaddr" and "adminaddr".) > > Hey... It works! 8-) > Thanks a lot!
However... It seems that the first server in the file is matched, always. With this: ============ userpass "jp" "-----" adminaddr "127.0.0.1:10000" monotone "mtn" "-kxxxxxxxx" server "phd" host "localhost" pattern "info.aleph0.phd.*" local "-d" "/home/jeronimo/monotone/phd.db" "*" server "main" host "localhost" pattern "info.aleph0.*" local "-d" "/home/jeronimo/monotone/main.db" "*" server "zat" host "localhost" pattern "zat.*" local "-d" "/home/jeronimo/monotone/zat.db" "*" ============== I tried to push a branch named "zat.portuguese", and the server matched was the first one (phd.db got a new branch, and phd.log had the usual netsync messages). I thought that usher would only match the last one (the only one that matches!) J. _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
