On Tue, Jul 17, 2007 at 10:03:00PM -0400, Richard Lowe wrote: > [forgot to Cc the list, sorry about you getting this twice Danek]
/me shakes fist :) > Don't use Mq with our tools. It should be safe to do (in that they'll > bail out and yell at you at the important junctures), but it isn't, to > my knowledge, being done, so there could be gaps. > > Webrev, certainly, doesn't work happily in an Mq-shaped world (where > both parent and child have patches applied, anyway) For what it's worth, I've been using mq quite happily on our packaging project, popping my work off the stack before syncing with our project gate, and so forth. I admit, I haven't been using cdm, but I have been using webrev, and it's been working just fine. Though I haven't run it at a time when my parent repo has changesets I don't. And my webrev -r work should make it much easier to not care what the parent has in it at all. Webrev -r qbase:qtip is quite handy! > This would mean it didn't back up in progress change (but would warn you > that it wasn't), and thus that you'd have to commit anything you'd want > to backup. I assume people do tend to have checked in what they intend > to back up anyway? I always thought it was a nice feature to have the g-files backed up as well, though I'm sure people can get used to it. On the other hand, once you've gone to the trouble of doing something special with the bundle, stuffing the output of hg diff somewhere alongside it probably wouldn't be all that onerous, either. Danek _______________________________________________ tools-discuss mailing list [email protected]
