> I have a general question. How do you maintain multiple uncommitted patches? > Suppose you are working on two or more different features / changes that > would be committed separately. How do you maintain these different changes > till they are committed (sounds like a transaction)? Do you make a copy of > the repository for each feature / change? This would be problematic if the > features overlap in the files that they touch.
There are two ways. You can maintain separate repositories each with their own mercurial queues and you can then commit them separately and merge once done. I deal with it by using a single mercurial queue and using guards. I regularly re-order things in my queue, and that does require fixing diffs, but it's not so bad. The key is that you should learn to use mercurial queues. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
