On Wed, May 18, 2011 at 5:14 AM, Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> wrote: >> >> I strongly believe git-svn should leave no trace. Nobody but the user >> using git-svn should know they're using git-svn to interact with an SVN >> repo. This allows users to stay under the radar of any idiotic rules >> (or knee-jerk reactions of FUD) their organization may have against >> using non-standard SVN clients. So far, it's worked out pretty well, >> git-svn users slowly and quietly develop clout and influence to migrate >> their repos from SVN to git. > > git-svn's maintenance of these files would be simpler if we used a > special file for that, say .git-svn-empty-dir, and teach dcommit to > ignore it. That way git clones can share it and git svn dcommit is > unimpaired. The only problem occurs when a new git-svn commits these, > and old git clones that and an old git-svn dcommits from that clone. > I'll let people more experienced than I come to a conclusion on this one. I can say I'm loath to spend a lot of time on this, given that it might all be replaced within two months by Dmitry Ivankov's GSoC project. - Ray -- 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