>> - In hindsight, one may see the items in this patch as unrelated, >> but I initially created this patch with the sole goal of adding >> large memory support to Ruby. It turned out I encountered a lot of >> issues throughout the code, and there are more to come. That being >> said, I have no problem using the "-X" option to separate these out >> to multiple changesets when I commit them. > > What I do when that happens is refresh my current patch, pop it, write > a patch that fixes whatever the issue is, refresh it, and then push my > first patch back on. Then everything stays seperated into minimal > logical units which makes history diving a lot nicer.
Another thing that you can do if lots of things wind up in the same patch is to manually pull the patch apart into multiple patches. It sounds like a pain, but it's really not that hard to do. Also, I don't think the -X option works when you're using mq because when you convert an applied patch to a changeset (using hg qdel -r), you're not actually doing a commit. Nate _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
