On Sun, Mar 04, 2007 at 10:27:39PM +1100, William Uther wrote: > I could modify clone so that it stored the database in "<working-copy- > name>.db". Or "<working-copy-name>.mtn-db".
The "official extension" (whatever that means) is ".mtn". (Also, random tangential note, we've tried to train ourselves to consistently use the word "workspace" instead of "working copy", at least as far as documentation and such goes.) > - It shows that mtn has another common use case where you want to > run a series of commands in a row. (Maybe I need to implement the > suggestion on the UI wiki page where monotone logs the commands used > with a timestamp in ~/.monotone/ somewhere and gathers it in > occasionally. Then we could use that as empirical data for UI design.) Check the archives -- this idea ran into problems because of concerns about users over-reacting to the whiff of big brother phone home data collection -- or even just mangled rumors thereof. I still would love to see this data somehow, but the naysayers have a point... -- Nathaniel -- Damn the Solar System. Bad light; planets too distant; pestered with comets; feeble contrivance; could make a better one myself. -- Lord Jeffrey _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel