darcs-2.1.98.2: a distributed, interactive, smart revision control systemSource codeContentsIndex
Darcs.Match
Synopsis
match_first_patchset :: RepoPatch p => [DarcsFlag] -> PatchSet p -> SealedPatchSet p
match_second_patchset :: RepoPatch p => [DarcsFlag] -> PatchSet p -> SealedPatchSet p
match_patch :: RepoPatch p => [DarcsFlag] -> PatchSet p -> Sealed2 (Named p)
match_a_patch :: Patchy p => [DarcsFlag] -> Named p -> Bool
match_a_patchread :: Patchy p => [DarcsFlag] -> PatchInfoAnd p -> Bool
get_first_match :: RepoPatch p => Repository p -> [DarcsFlag] -> IO ()
get_nonrange_match :: RepoPatch p => Repository p -> [DarcsFlag] -> IO ()
get_partial_first_match :: RepoPatch p => Repository p -> [DarcsFlag] -> [FileName] -> IO ()
get_partial_second_match :: RepoPatch p => Repository p -> [DarcsFlag] -> [FileName] -> IO ()
get_partial_nonrange_match :: RepoPatch p => Repository p -> [DarcsFlag] -> [FileName] -> IO ()
first_match :: [DarcsFlag] -> Bool
second_match :: [DarcsFlag] -> Bool
have_nonrange_match :: [DarcsFlag] -> Bool
have_patchset_match :: [DarcsFlag] -> Bool
get_one_patchset :: RepoPatch p => Repository p -> [DarcsFlag] -> IO (SealedPatchSet p)
checkMatchSyntax :: [DarcsFlag] -> IO ()
Documentation
match_first_patchset :: RepoPatch p => [DarcsFlag] -> PatchSet p -> SealedPatchSet pSource

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 :: RepoPatch p => [DarcsFlag] -> PatchSet p -> SealedPatchSet pSource
match_second_patchset fs ps returns the part of ps before its second matcher, ie the one that comes last dependencywise.
match_patch :: RepoPatch p => [DarcsFlag] -> PatchSet p -> Sealed2 (Named p)Source
match_a_patch :: Patchy p => [DarcsFlag] -> Named p -> BoolSource
match_a_patch fs p tells whether p matches the matchers in the flags fs
match_a_patchread :: Patchy p => [DarcsFlag] -> PatchInfoAnd p -> BoolSource
match_a_patchread fs p tells whether p matches the matchers in the flags listed in fs.
get_first_match :: RepoPatch p => Repository p -> [DarcsFlag] -> IO ()Source
get_nonrange_match :: RepoPatch p => Repository p -> [DarcsFlag] -> IO ()Source
get_partial_first_match :: RepoPatch p => Repository p -> [DarcsFlag] -> [FileName] -> IO ()Source
get_partial_second_match :: RepoPatch p => Repository p -> [DarcsFlag] -> [FileName] -> IO ()Source
get_partial_nonrange_match :: RepoPatch p => Repository p -> [DarcsFlag] -> [FileName] -> IO ()Source
first_match :: [DarcsFlag] -> BoolSource
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.
second_match :: [DarcsFlag] -> BoolSource
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 :: [DarcsFlag] -> BoolSource
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 :: [DarcsFlag] -> BoolSource
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?
get_one_patchset :: RepoPatch p => Repository p -> [DarcsFlag] -> IO (SealedPatchSet p)Source
checkMatchSyntax :: [DarcsFlag] -> IO ()Source
Produced by Haddock version 2.4.2