2 - improve e-mail and tag parsing
3 - try out git-fast-import's 'checkpoint' command
4 - get error checking up to Git.Write level
7 - error recovery. hmm, almost done - need to tell user how to recover, and
8 need to verify the darcs2git branch somehow.
9 - add some options. nice to have:
10 - -f flag for working from a dirty repository (experts only)
11 - -v flag -- be verbose
12 - store source repository in the destination so a simple
13 darcs2git suffices for updating.
15 - add option to pull from a certain tag.
16 (need to figure out how to get the corresponding tree. hmm. maybe it's
17 possible to start with a current pristine tree and work /backwards/,
18 creating the commits when we got far enough?)
19 - add some meta-information to initial commit?
21 old todos - might apply to Git.Fast as well:
24 - maybe add verbosity flag
25 - find git path with configure or similar
26 - add option for alternative error handling in 'git'
27 - get rid of rev / getRev / putRev - it doesn't belong there; either
28 add an extra state type argument to Git or use StateT in Git.Write
31 - track pref changes? Sadly, @apply (ChangePref _ _ _)@ looks for a
32 _darcs/pref directory in the repository, so this requires some hack
33 - improve email extraction - currently "droundy@darcs.net" ends up as
34 droundy@darcs.net <> -- i.e. the e-mail address is empty instead of
37 - only the last of duplicate tags will be kept. this is a problem because
38 the mapping of tag names is not injective.
39 - error messages for dirty repositories are awful