First, the question: How can one list the revision IDs within a monotone database without having a working copy of the tree available?
Now, the motivating scenario. I have a small project that's accumulated a half dozen revisions. One of my coworkers prepares a databases, pulls my project over, and now has a database available with a copy of my work. She now wishes to check out a working copy of the tree to play with. She doesn't want to work on the latest revision, though; in fact, she wants the first revision available in the database. At first I thought this would be no problem. The "checkout" command respects a "revision" argument. But how can we inspect the set of available revisions? I've combed the command reference and can't figure out how to "log"-like action without first checking out a working copy -- albeit not the one we're actually looking to fetch. If the project had thousands of files, fetching that spurious scratch copy would be huge waste. I don't mind the long hash strings as revision IDs. It's getting access to those IDs has me stumped. -- Steven E. Harris _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
