On Sat, 2006-10-28 at 18:23 +0200, Ulf Ochsenfahrt wrote: > Hi all! > > I've got a few questions. Some of these may already have answers, others > may not. I looked into the manual and checked the monotone built-in > help, but found no easy answer to these. > > - How does monotone select a (default) key to sign?
If you only have one key it uses that. There's also a get_branch_key hook that should at least work for commits. (it probably won't work for netsync, and I don't know about adding certs to revs that already exist) > - How can I find out which? I don't know that you can at the moment. > - Why is "automate get_option" not described in the manual? I don't know. It should be; this is a bug. > - Why does "automate get_option key" return an empty string? If you give '--key=foo' it returns 'foo'. I'm assuming that all it does is say what options were given on the command line, but I haven't actually checked the code. > - How can I add a directory non-recursively? ...why doesn't add take --depth? Anyway, aside from changing that, you can probably just add the directory and then drop all its children. > - How can I suppress the automatic commit message dialog and get an > error instead if no message was given on the command line? Probably by giving it an edit_comment hook that just returns false/nil (don't remember which). This could go in _MTN/monotonerc, or in some other file that you specify with --rcfile if you want your users to be able to run monotone operations on their workspace manually and get "normal" behavior. -- Timothy Free (experimental) public monotone hosting: http://mtn-host.prjek.net _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
