[darcs-users] Ignoring patches

[Phil Frost]

On Tue, May 03, 2005 at 11:14:49AM -0400, Daniel Burrows wrote:
>   Is there a way to get either "darcs record" or "darcs push"/"darcs send" to 
> permanently ignore one or more patches?  i.e., set it up so that a particular 
> patch exists in my repository but is never considered for distribution to 
> others.
> 
>   A use case would be something like this:
> 
> -#define VERY_VERBOSE_DEBUGGING 0
> +#define VERY_VERBOSE_DEBUGGING 1
> 
>   I don't want everyone else to get spammed with useless (to them) debug 
> messages, so I'd rather not push this patch to other repositories at all.  
> But I also don't want to accidentally record this as part of another patch 
> ('record' will prompt about this hunk, and 'record -a' will put it in 
> automatically); for that reason, I'd like to record it locally so that darcs 
> knows about it and quits asking me whether to record it.  So ideally, what 
> I'd imagine is a "darcs embargo" command, or maybe something in _darcs that I 
> can edit, that keeps certain patches from being considered as 'psuh' targets.
> 
>   Ideally, of course, I'd also get a warning if I was about to create a patch 
> that depended on the "quarantined" patch, so I could temporarily back it out 
> and put it back in after the record.  In the cases where I'd like to do this, 
> I hope that no other patch would ever depend on the quarantined one, but it 
> seems like patches that have nearby context or that move the #define around 
> might cause problems.  (I haven't quite worked out how dependencies are 
> calculated yet)
> 
>   Daniel

How about a --not-patches option to push, send, and friends? People can
then adopt their own convention, say starting the patch name with
LOCAL:, and then put a line in prefs to avoid typing the option always.