Maris, Rob writes: > Currently hunks are identified as blocks of text lines that are separated > by at least one unmodified line. However, I'd want to create a sort of > recipe on a per-repo basis that allows me to specify a sort of field > separators that should be recognized by the hunk identification algorithm. > > Example: I'd want to manage object library files (graphic objects, > organized in libraries stored as ASCII text) through darcs. Darcs should > only identify single hunks using specification in the user recipe. Goal: > prevent the creation of too many hunks caused by alternating lines within > an information entity that are modified, and lines in between that are not > modified.
What do you mean be "too many hunks"? Why is "many hunks" a problem? _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
