IE. Section D.8 of the elisp manual.

Thanks to Jonas Bernoulli <jonas@bernoul.li> for the push.

[commit-patch] Use --force when patching back to the clean version so if something goes wrong it doesn't ask interactive questions.

[commit-patch] Use --relative with "git diff" so that commit-partial doesn't silently fail when you in a subdirectory.

"git apply" seems to filter the diff so that only files within the current
directory (and its descendants) get applied. It (crazily) does this silently
and there doesn't seem to be an option to override this.

The other option would be to cd to the project root just before calling "git
apply" but I think it's more intuitive to diff from your current
directory--just cd to the root yourself if you want to see the whole
project's changes.

[commit-patch] Support svn 1.7 which apparently doesn't scatter .svn droppings in every subdirectory. (Thanks sneakypete81)

Prevent mercurial from adding/removing all files

Fixes #2

[commit-patch] Use Monotone's --without-header option instead of looking for diffs that are exclusively comments.

[commit-patch] Avoid running 'interdiff' and 'patch -R' also when the working patch is just a series of comment lines.

'mtn diff' will output three comment lines when there are no changes.
patch ignores them, so should we.

[commit-patch] Use lsdiffs -s option to keep track of added, removed, and changed files in the patch so we can use them appropriately.

[commit-patch] VCS Add and Remove needs to happen after the patch has been applied to the directory.

Thanks to Richard Levitte <richard@levitte.org> for pointing this out.

Patch fails when the input has just a single \n in it which is what happens when
we do "darcs diff a" and "a" doesn't exist yet.

It's cleaner and makes it easy to look for empty files (next patch) but it
doesn't scale as well since both working and non-committed patches have to fit
in memory (which probably doesn't matter since most patches aren't massive).