[prev in list] [next in list] [prev in thread] [next in thread] 

List:       darcs-devel
Subject:    [darcs-devel] [issue2661] change the "after the latest clean tag" limitation for	obliterate and unre
From:       Ben Franksen <bugs () darcs ! net>
Date:       2020-10-21 19:17:53
Message-ID: 21f5c4f6-ce96-6ede-de80-665c7678688a () online ! de
[Download RAW message or body]


Ben Franksen <ben.franksen@online.de> added the comment:

A slight correction wrt the actual behavior.

If the user specifies a matching option that counts as a "fist matcher"
i.e. one of the --from-xxx or --index=N-M variants (or the singular
match options but they are not supported for these commands), then the
restriction to patches after the last clean tag is not in effect. Same
if --not-in-remote is in effect; in which case the --from-xxx or
--index=N-M are ignored, but plural versions of "nonrange" match flags
(--patches or --matches) do take effect; because these are (also)
"nonrange matchers" and these are handled by the patch selection code.

See Darcs.UI.Commands.Util.preselectPatches for details, as well as
Darcs.Patch.Match.{firstMatch,nonrangeMatch}.

Any work on this ticket should include a cleanup of this mess.

__________________________________
Darcs bug tracker <bugs@darcs.net>
<http://bugs.darcs.net/issue2661>
__________________________________
_______________________________________________
darcs-devel mailing list
darcs-devel@osuosl.org
https://lists.osuosl.org/mailman/listinfo/darcs-devel
[prev in list] [next in list] [prev in thread] [next in thread]