|writePatchSet is like patchSetToRepository, except that it doesn't
touch the working directory or pristine cache.
|Gets the unrecorded changes in the given paths in the current repository.
|This fuction is unsafe because it accepts a patch that works on the tentative
pending and we don't currently track the state of the tentative pending.
|patchSetToRepository takes a patch set, and writes a new repository in the current directory
that contains all the patches in the patch set. This function is used when 'darcs get'ing a
repository with the --to-match flag and the new repository is not in hashed format.
This function does not (yet) work for hashed repositories. If the passed DarcsFlags tell
darcs to create a hashed repository, this function will call error.
A PatchSet is in reverse order, plus has information about which
tags are clean, meaning all patches applied prior to them are in
the tag itself, so we can stop reading at that point. Just to
clarify, the first patch in a PatchSet is the one most recently
applied to the repo.
PatchSets have the property that if
(info $ last $ head a) == (info $ last $ head b)
then (tail a) and (tail b) are identical repositories
Does this mean that in a patch set such as [[a b t1 c d e t2][f g
t3] [h i]], t1, t2 and t3 are tags, and t2 and t3 are clean?
Can we have PatchSet with length at least 3?
|PatchInfoAnd p represents a hope we have to get a
patch through its info. We're not sure we have the patch, but we
know its info.
|Sets scripts in or below the current directory executable. A script is any file that starts
with the bytes '#!'. This is used sometimes for --set-scripts-executable, but at other times
--set-scripts-executable is handled by the hunk patch case of applyFL.
|Produced by Haddock version 2.4.2|