2 - improve e-mail and tag parsing
5 - track pref changes? Sadly, @apply (ChangePref _ _ _)@ looks for a
6 _darcs/pref directory in the repository, so this requires some hack
8 - only the last of duplicate tags will be kept. this is a problem because
9 the mapping of tag names is not injective.
12 - find git path with configure or similar
16 - add more options. nice to have:
17 - -f flag for working from a dirty repository (experts only)
18 - store source repository in the destination so a simple
19 git-darcs-import suffices for updating.
21 - add option to pull from a certain tag.
22 (need to figure out how to get the corresponding tree. hmm. maybe it's
23 possible to start with a current pristine tree and work /backwards/,
24 creating the commits when we got far enough? -- note, even darcs itself
25 has problems with this for darcs-2 repos)
26 - add some meta-information to initial commit?
27 - fix author tag for initial commit (the file date has wrong format)
28 - a commit can produce several blobs per file, most of which end up dangling.
29 that's inefficient (to the point where git gc blows up a repro to 15 times
30 its final size, because it extracts these dangling blobs to single objects),
31 and probably can be fixed fairly easily by keeping around a list (set) of
32 changed files. Note: As a workaround, run git repack -a -d before git gc