|
|
|
|
Synopsis |
|
|
|
Documentation |
|
|
match_first_patchset fs ps returns the part of ps before its
first matcher, ie the one that comes first dependencywise. Hence,
patches in match_first_patchset fs ps are the ones we don't want.
Question: are they really? Florent
|
|
|
match_second_patchset fs ps returns the part of ps before its
second matcher, ie the one that comes last dependencywise.
|
|
|
|
|
match_a_patch fs p tells whether p matches the matchers in
the flags fs
|
|
|
match_a_patchread fs p tells whether p matches the matchers in
the flags listed in fs.
|
|
|
|
|
|
|
|
|
|
|
|
|
first_match fs tells whether fs implies a first match, that
is if we match against patches from a point in the past on, rather
than against all patches since the creation of the repository.
|
|
|
first_match fs tells whether fs implies a second match, that
is if we match against patches up to a point in the past on, rather
than against all patches until now.
|
|
|
have_nonrange_match flags tells whether there is a flag in
flags which corresponds to a match that is non-range. Thus,
--match, --patch and --index make have_nonrange_match
true, but not --from-patch or --to-patch.
|
|
|
have_patchset_match flags tells whether there is a patchset
match in the flag list. A patchset match is --match or
--patch, or --context, but not --from-patch nor (!)
--index.
Question: Is it supposed not to be a subset of have_nonrange_match?
|
|
|
|
|
|
Produced by Haddock version 2.4.2 |