Re: Hg sure is weird!

ST> But suppose it was a largish change that was actually a sequence of ST> several commits? Now export is no help, is it? Nope, you're right--you'd need to check the log to make sure you have the right parent, then use "hg diff". ST> "hg log" output is also filled with (usually) uninteresting merge ST> logs FWIW, you can use -M to suppress merge changesets. Of course, that removes one of the clues that the changesets aren't all on the same branch.:-/ ST> and interposes fetched revisions in the line of development we ST> really want to see. It's possible that the folks on the Mercurial user list might have some hints for how to make this easier to deal with. Using named branches might help. I don't have much advice because I don't usually have to deal with branches. The development guidelines for the Solaris kernel and core userland require no "merge turds". So we have tools to trim off side branches. Pushing to the main gate typically just adds one changeset to the end of the default branch. Maybe "hg log" needs an option that tells it to organize changesets by branch, rather than simply showing them in the same order that they appear on disk. mike _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta