Andrew Myrick schreef:
I've been testing git-svn v1.6.6-rc3's mergeinfo support on a large
svn repository (60,000+ revisions, 20+ GiB) that uses a very
branch-heavy integration model in which every change gets its own
branch before being committed to trunk. As a result of the model,
there are currently over 1000 lines in the svn:mergeinfo property on
trunk.
Just wondering: Isnt this workflow stalling svn itself alot too?
And also:
Do you delete the branches after you reintegrated them? If so, I think
its safe for you to cleanup the svn mergeinfo once in a while. That
should not affect 'svn log -g' because the mergeinfo is still there in
older revisions. I think svn benefits from this too...
--
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