Russ Brown <pickscrape@xxxxxxxxx> writes: > I'm having some trouble with using git-svn to fetch a repository, and I > think it's because the repository doesn't store branches as a flat list > directly under the 'branches' directory. > > Basically, we have a structure like this: > > | > +-trunk > +-tags > +-branches > + category-a > + branch-a > + branch-b > + category-b > + branch-c > + branch-d > > etc. category-a and category-b are simple directories created using svn > mkdir. The branches are created using svn cp. > > It helps us to organise the branches better, but the rationale is > besides the point. The problem is that git-svn seems to want to > treat category-a and category-b as branches, which isn't right at > all. As a result, git-svn seems to skip most (if not all) revisions > that occur in these directories and creates a lot of entries in > unhandled.log. So what did you specify in your .git/config file regarding the svn structure? -- David Kastrup - 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
