Jason Dagit <[email protected]> writes: > I'm not sure where to go next with this information. One idea I had, > was to not calculate/create hunk patches until they are absolutely > needed.
I edit two files "foo.c" and "bar.c", then run "darcs record". Looking at the diff it presents for foo.c, I see a different (unrelated) bug, and fix it in both foo.c and bar.c. I then press "y" to accept the first hunk. Should the second hunk include the second bugfix? Eager won't include it, lazy will. This is particularly critical if the second bugfix involves re-editing the same lines of bar.c as were modified by the original edit. I think making record get hunks lazily is a Good Thing, but bear in mind it might break existing workflows (as above) that (ab?)use the existing behaviour. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
