On 6/20/07, Eric Wong <normalperson@xxxxxxxx> wrote:
Martin Langhoff <martin.langhoff@xxxxxxxxx> wrote: > First -- kudos to Eric Wong and company: git-svn can deal with the odd > errors and invalid chunks of XML or UTF-8 that SVN spits at me every > once in a while. And it "just works" in 99% of the situation. Great > stuff. You're welcome. At the same time I'm not reallu sure what you mean by "odd errors and invalid chunks of XML or UTF-8 that SVN spits at me" unless it's some joke about SVN I'm not getting :)
Oh - the Squirrelmail SVN repo is one of those that have commits that SVN itself cannot read due to invalid data. So git-svnimport, by virtue of using the Perl SVN bindings, fails to import it. git-svn, by some other virtue, imports it perfectly ;-)
> [svn-remote "svn"] > url = http://squirrelmail.svn.sourceforge.net/svnroot/squirrelmail > fetch = trunk/squirrelmail:refs/heads/svn/trunk > branches = branches/*/squirrelmail:refs/heads/svn/* > tags = tags/*/squirrelmail:refs/tags/svn/* git-svn expects 'refs/remotes/' in the local ref name. Otherwise, the left-hand side is correct.
Good to know!
> and when I do that -- trunk and branches do what I want, but tags > aren't imported anymore. :-/ Now its odd to me that trunks and branches even works with those ref names.
I'm lucky then ;-) My reason for the "alternative" locations is to match a bit better the v1.5.0 behaviour re branches, tags and remotes, and to run the import directly into a bare repo on git.catalyst.net.nz - Tags, by virtue of landing under refs/remotes are being treated as heads rather than tags. That's why I want to have them in refs/tags/<bla>/* - If branches + trunk end up in refs/remotes then my bare repo / gateway doesn't work well - -refs/remotes aren't cloned or fetched - gitweb refuses to show those heads/tags (maybe it's because it's an old version?) cheers, martin - 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