How about using git itself to keep some of this information? I'll just
throw this idea out there; might or might not make any actual sense.
Create a new "git-svn metadata" branch. This branch contains a fake
directory (never intended for checkout, though you could do it) that
has a "file" for each svn revision. The filename is just the svn
revision number, maybe divided into subdirectories in case you want to
check the branch out for debugging purposes or whatever. The contents
are the git commit SHA1 and whatever other metadata you want to keep
in the future.
The advantage of doing it this way? You can pass around svn metadata
using the normal git fetch/push tools, query the metadata using "git
show", etc. In terms of data integrity, it's as secure as anything
else in a git repository, much more so than a separately maintained db
file under .git.
Along similar lines, a separate branch where the filenames are commit
SHA1s and the file contents are the stuff that currently gets written
into the git-svn-id: lines would mean no more need to rewrite history
when doing dcommit, and thus easier mixing of native git workflows and
interactions with an svn repository.
It would be great if you could clone a git-svn repository and then do
"git svn dcommit" from the clone, secure in the knowledge that things
will stay consistent even if the origin gets your changes via "git svn
fetch" rather than from you.
-Steve
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
