[Twisted-Python] the repository metadata of inevitability

[meejah]

Glyph <glyph at twistedmatrix.com> writes:

> If I do this with filter-branch, though, that's going to break git-svn
> support entirely because the hashes won't match, right?

"Maybe". I haven't tried that. Certainly the hashes won't match, but the
git-svn-id tags in the commit messages will still match. So, *could*
plausibly work, but I don't recall if I ever tried additional pulls from
svn after filter-branch (we were migrating wholesale to git in "one"
step).

Another way is to re-do the git-svn clone, but provide a svn->git
mapping. You can do this with a program if they're "regular" (e.g. if
you can just add "@twistedmatrix.com" to the SVN ids). Or you can
provide an explicit file mapping SVN -> name + email.

Not sure how long your clones take, but I know they can take a
looooooong time, so might be worth trying the filter-branch way
while-u-wait for a re-clone ;)

Anyway, the option is --authors-prog to "git svn fetch" (or
--authors-file I think if you do the static mapping way?)

With the program, you get the SVN id as the only arg, and spit out
"first last <email at example.com>" on stdout.

I documented a bunch of my adventures in this regard (migrating a large
SVN repo to Git) on my blog:

   https://meejah.ca/blog/migrating-svn-to-git

Unfortunately, I can't simply release all my scripts for that, but I
could "use it as inspiration" if any of those steps sound useful to
Twisted.

> <https://github.com/twisted-infra/twisted-buildbot-configuration/> is
> available for your perusal if you want to find it out :).

Okay, I'll take a look.

-- 
meejah