Quoting "Beckmann, Brad" <[email protected]>: > Thanks everyone for the comments. I won't be able to check in my > patch(es) today, but will work on it more next week and try to > commit them in a week or two. > > First to answer Nate: > - 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. Gabe _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
