Sanity, Inc.

I have been experimenting with this on a large existing darcs repos and have the following minor fixes which I can send you - please email me Steve if you would like me to send a git bundle of these commits (I can't find an email address on this site):

- Fixed darcs boringfile expression to correctly exclude .git repository from whatsnew

- Cope with 'darcs setpref' in source repository which overrides the boringfile under _darcs with one under source control
When this happens it removes the patterns we have added to exclude the .git directory.
Handle it by deleting the _darcs/prefs/prefs file whenever it is recreated by pulling patches.

- Force git commits to be recorded even when git can't see any changes
It's possible in some circumstances (e.g. with merge conflicts) to have non-tag darcs patches which don't create or change any files when pulled individually, or which only create/remove empty directories,

- Make the check for an empty git repos work even if git-gc has been run

- Show full output from 'darcs whatsnew' when it reports changes

- When re-pulling to get new patches, consider all patches instead of stopping at the first that is already in git

- More verbose output when deciding which patches to pull