| Issue 10: | Patch part dependencies | |
| 1 person starred this issue and may be notified of changes. | Back to list |
We ought to have a way to record parts of patches. Darcs can do this. In order to do so, though, we need a way to determine which patch-parts need other patch-parts to record. (Darcs also does this!) Sketch of how this would work: Hunk: no dependencies; all hunks are independent. However, there is some offsetting to do if not all hunks are taken. File: no dependencies except within Hunk. Hierarchy: *DelDir depends on DelFile Dir/* recursively *ChgItem after an AddFile depends on the AddFile *DelFile might depend on a ChgItem removing everything *We need to be able to record different parts of ChgItems independently *MovItem depends on a DelFile or DelDir of the target, if it exists (if you decide that it should still be there, you can't move something there!) *others? This list is probably incomplete
May 9, 2009
Project Member
#1
alexande...@gmail.com
May 9, 2009
(No comment was entered for this change.)
Labels:
-Type-Enhancement Type-Testing
May 17, 2009
Testing has revealed some potential problems, so upping the priority.
Labels:
-Type-Testing -Priority-Medium Type-Defect Priority-High
May 18, 2009
Specifically, comming an add causes a "corrupt patch file" bug.
May 18, 2009
(No comment was entered for this change.)
Labels:
-Priority-High Priority-Critical
May 22, 2009
Fixed by changing the Hierarchy depends1 function AND by switching to Data.Graph's topological sort functionality for the psort function. This probably needs more testing...
Status:
Fixed
|