Hi Thomas,

Thanks for the reply.  I ended up creating a new folder with a
different name and copying the good branches into it, then I deleted
the old folder.  So I ended up with:

/branches/myProject-python-client/branchX-failed
/branches/myProject-python-client/branchX
/branches/myProject-server/server-branch

If the new folder had the same name as the old folder git would pick
up the history of the server-branch, even if the actual folder was
totally new and never had held that branch.  So that myProject-client
name is forever tainted, but oh well.  At least I've got things on
stable ground again.

Cheers,
-n8

On Sep 1, 11:19 pm, Thomas Ferris Nicolaisen <tfn...@gmail.com> wrote:
> Hi Nathan,
>
> Yeah, I often get problems with --ignore-paths too. Sometimes I wonder if it
> works at all.
>
> Did you consider limiting the revisions included in the clone? You can pass
> in a revision range to git-svn fetch like this:  -r12033:HEAD

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Reply via email to