>Hopefully, at least. But with a re-export you would have to re-import
>any changes already made afterwards. And you would have have to
>re-validate everything again since it would be a new import from
>scratch. So it seems like a worse way to do it.
Maybe.
>Of course, you could do both and verify that you actually do get the
>same end result (which should only amount to comparing the SHA:s of
>the heads and tags)...
True.
Before we do anything about it, I'd like to know if there are any
other known conversion bugs with the Pike git repository than:
* The TZ offsets are three decimals when they should be four.
- git-fsck complains about ~ all commits.
- Some third party git tools may get confused.
* The automatically generated .gitignore files contain extraneous
whitespace at EOL in some cases.
- Files that are supposed to be ignored by git aren't.
In particular, do any of the email addresses or author names need to
be adjusted?
