On Nov 01, 2005 05:35 AM, Robert Anderson <[EMAIL PROTECTED]> wrote: > I'll throw this one into the ether again:
> If there was a way to take a tree and split out changes hunk by hunk > into two or more trees (including a null tree), wouldn't the power of > changesets really finally be there in a way that's far more useful? This is the default behaviour in darcs -- when you do 'darcs record', it will iterate through each hunk, rename, etc, and ask if you want to include it in the changeset. You can also do, 'darcs record -a', to record everything. Even if you are very careful about creating clean changesets, this is a useful feature. For example, sometimes the build process will patch files, and you don't want to commit those changes. Running: 'make clean && tla commit && make' Can take a very long time (hours) for something like x.org or OOo. j. _______________________________________________ Gnu-arch-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/
