On Mon, Oct 09, 2006 at 09:56:11AM +0200, Korusef wrote: > On 10/7/06, Tommy Pettersson <[EMAIL PROTECTED]> wrote: > ... > >The easy way to implement ignored patches is with an ignore list > >in _darcs/prefs/. I think this would absolutely be the best to > >start with. It has some theoretical limitations, but it would > >require much more complicated changes to get around them, and we > >don't know if there really is any need for those yet. But it can > >be good to know about them, and to express them in the > >documentation. > > Yes the ignore file is IMHO the best solution, it'll be also very > similar to my current practice, > when I give these patches special name, usually "local branch", > "DEBUG > branch", etc., and put proper rule for push/pull matches in the > _darcs/prefs/defaults file?
Huh. The main problem with my original patch was that it ignored dependences, which messed things up. I bet if you put the ignore support in something like SelectChanges.lhs:patches_to_consider it would automatically handle this case. This would probably be a first pass though. Because this might hide important patches from you before you chose to ignore some previous patch. It might be nice if ignored patches are hidden, but their dependencies are not. Then, if you selected a patch that depends on an ignored patch, it could inform you that you can't until you unignore a dependency. Or if ignoring/unignoring is eventually an option during patch selection (which would be nice), you could unignore it there. I think this idea was already tossed around a while back, but I'm mentioning it again just in case. - Zachary P. Landau <[EMAIL PROTECTED]> GPG: gpg --recv-key 0xC9F82052 | http://divineinvasion.net/kapheine.asc
signature.asc
Description: Digital signature
_______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
