On Tue, Jan 31, 2006 at 07:38:38AM -0800, John Meacham wrote: > On Tue, Jan 31, 2006 at 11:32:28AM -0400, [EMAIL PROTECTED] wrote: > > > Any patches which matched that query would be those that violate your > > > "domains" restriction. > > > > ... except for the logic error so that only a patch which touched all five > > domains would match... > > and that the point is to keep devopers from creating such patches in > the first place, not identifying them after the fact. > > John
Maybe I'm just being dense, but what about just a simple record prehook which has access to the repo, or somehow accepts the filenames being recorded. If the prehook fails, no patch for you. For you, the prehook can scan for changes to multiple domains. For the rest of us, we can check for other things. My impression (and I don't presume to have any weight around here, granted) is that this is way too specific a thing to get into the darcs code. Which also reminds me, why not use 'darcs setpref test'? I didn't read this whole thread, feel free to ignore the question if it has been asked and answered. -- Jason M. Felice Cronosys, LLC <http://www.cronosys.com/> 216.221.4600 x302 _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
