Il giorno lun, 12/10/2009 alle 11.20 -0700, Eric Wong ha scritto:
> First I thought this was a problem fixed in
> 83c2fcff214fe89649fcd88e095d9961a36b53dd (git v1.6.2 or later),
> but then I tried running it just to make sure.
thank you for taking the time
> This is a namespace conflict, the "trunk" ref is conflicting with a
> (what seems to be a miscreated) branch named "trunk". I anticipated
> this problem originally but figured it was rare/uncommon enough that I
> didn't want to burden users by prefixing all branches with something:
>
> ------------------------------------------------------------------------
> r25364 | michael.hashimoto | 2009-01-21 14:06:53 -0800 (Wed, 21 Jan 2009) | 1 line
> Changed paths:
> A /plugins/branches/trunk
>
> Created directory 'plugins/branches/trunk'.
> ------------------------------------------------------------------------
> r25365 | michael.hashimoto | 2009-01-21 14:07:15 -0800 (Wed, 21 Jan 2009) | 1 line
> Changed paths:
> D /plugins/branches/trunk
>
> Removed plugins/branches/trunk
>
> Since it looks pretty obvious that "trunk" was miscreated here from the
> revision history, you can skip these two revisions in your import by
> recontinuing the clone with "git svn fetch -r25365:HEAD"
I thought it could be a problem like this but I asked before re-fetching
all the repository (just to be sure)..
unfurtunately I already deleted all the .git directory so i'll have to
start again...
> Replace:
> [svn-remote "svn"]
> branches = plugins/branches/*:refs/remotes/svn/*
>
> With:
>
> [svn-remote "svn"]
> branches = plugins/branches/*:refs/remotes/svn/branches/*
>
> I didn't do this by default since I figured very few people would create
> a branch named "trunk" (and those who did, did it accidentally as it
> seems to be the case here).
>
> Hope that helps.
Yes it really help...
But I'll change it like this instead:
[svn-remote "svn"]
url = http://svn.liferay.com/repos/public
fetch = plugins/trunk:refs/remotes/svn/master
branches = plugins/branches/*:refs/remotes/svn/*
I think it will do as long as they didn't created some branch named
"master" :)
In this case the repo was public, what should I do to debug some git-svn
issue like that if I encounter a problem with a non-public repo?
May be there is some debug flag I could enable? Or I had to
guess/explore the svn tree?
thank you Eric
regards,
Daniele
--
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