Lapo Luchini wrote:
Daniel Carrera wrote:
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 c
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
Daniel Carrera <[EMAIL PROTECTED]> writes:
[...]
> My current solution is Darcs, which indeed makes the above easy. When
> I run "darcs record", darcs shows me the changes one at a time, and I
> can tell it which ones to include in the patch. Another equally good
> solution is: (1) record the cur
