Sam Vilain pisze: > It's up to the git-svn user to make sure that they prepare the refs to > be what git-svn expects. This is something probably requiring more > documentation and/or git-svn features to be easier. What I was asking if we should add trunk ref to svn mirror so others cloning it will have 'origin/trunk' reference created automatically during clone process so no extra steps would be needed. To be honest, I don't understand how Git exactly handles all this refs mapping and rewriting (e.g. during cloning). Having said that, I cannot foresee all possible implications of choosing particular method of solving current issues thus asking you. >> Would it be the best practice? > > Well, obscure stuff should never really be best practice. The best practice > is to have a single git repository that is where the svn -> git migration > happens. And git-svn could perhaps auto-init based on information in the > commit log or something. Best practice is to enhance the tool to work the > way it Should(tm) :) Cannot follow you here. We want single svn mirror but at the same time we want to our committers to be able to push back to svn. What has been already proposed satisfies my need apart from the fact that currently there is small problem with our mirror setup. -- Best regards, Grzegorz Kossakowski -- 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
