Daniel Carrera wrote: > Anyways, at this point I would like to commit the changes related to > Issue_B. But I already have a bunch of changes for Feature_A and I don't > want to mix the two together.
In those cases I usually stop working in directory Feature_A/ and do a fresh new checkout (of the last "stable" release on which the fix must be applied) in directory Issue_B/, then do the quick fix, commit it, and delete the directory Issue_B/. Then I continue working on Feature_A/ until it is ready for commit, I commit it, and only then I "mtn merge". This of course has sense only if Issue_B/ is "quick & easy", if Issue_B itself is worth quite a few commits, then creating a branch is probably much better =) -- Lapo Luchini - http://lapo.it/ “C is quirky, flawed, and an enormous success.” (Dennis M. Ritchie) _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
