Hello Jorg,
It's pretty easy to change the author on the SVN side:
svn propset --revprop -rREV svn:author 'newAuthor' SVN_URL
But this change has no effect on Git side and on overall license users counting, as we count Git
authors.
But it's hard to change author in Git because that would mean different SHA-1. In this case one can
1. Fix the author in SVN.
2. Discard current Git repository.
3. Install SubGit from scratch to a new directory or rebuild existing
one with:
$ subgit install --rebuild path/to/git/repository
Note that SHA-1 hashes will be different and the repository will need to be re-cloned.
What about license: SubGit counts Git committers for the last year (and those wrong committers,
too). You can always check what Git committers are there with
$ subgit register --print-committers path/to/git/repository
When the number of committers is exceeded, SubGit starts showing warnings and after 28 days stops
working.
See this article for details:
https://blog.subgit.com/subgit-license-keys/In cases like yours if our users can't fix the problem themselves with --rebuild, we usually issue a
new key, e.g. for 11 users instead of 10.
I hope, this information helps.
--
Dmitry Pavlenko,
TMate Software,
http://subgit.com/ - git-svn bridge