So is the basic problem that the history of the branch is unknown and
we have to retrieve the history?
Robert
On Jul 25, 2009, at 5:51 AM, Eric Wong wrote:
Robert Zeh <robert.a.zeh@xxxxxxxxx> wrote:
I am seeing git svn fetch repeatedly retrieve the same Subversion
revisions when it finds branches in our Subversion repository. We are
using the standard Subversion repository layout, with top level /
trunk,
/tags, and /branches directories (and the git repository was
created with
'git svn init -s'). However, the problematic branches are often
copies
made from a subdirectory inside of trunk, instead of trunk.
Hi Robert,
Yes, this is a known problem with some repositories and there's no
automatic/easy[1] way to handle it with globbing tags/* or branches/*.
You can try to track each tagged project independently or to setup
individual fetche lines (like the one generated for trunk). in
.git/config for each tag/branch.
[1] - Unfortunately SVN allows way too much freedom and thus ambiguity
in how it treats tags/branches and that doesn't allow mapping those
things to git very easily.
--
Eric Wong
--
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