- ...patch).4.1
- If
you look inside _darcs you will find files or directories named
patches and inventories, which store all the patches
ever recorded. If the repository holds a cached pristine tree, it
is stored in a directory called pristine.hashed.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...4.2
- Revert can undo precious work in a blink.
To protect you from great grief,
the discarded changes are saved temporarily
so the latest revert can be undone with unrevert.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... it.4.3
- darcs even has a special command, trackdown
that automatically removes patches
until a specified test no longer fails.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... repository.4.4
- It will omit patches already depended upon by other patches,
since they will be indirectly depended upon anyway.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...
push5.1
- But it affects the repository and working directory targeted by
the push
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...
send5.2
- As for the other end, see apply
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...
put5.3
- Creates a new repository
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ... back.5.4
- The patch file itself is not actually deleted, but its
context is lost, so it cannot be reliably read--your only choice would be
to go in by hand and read its contents.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.