[git-users] Re: git-svn: server-side madness has killed my buzz
I can't get the right use of the --ignore-paths too after dozen of attempt. The strategy i used is the same as n8gray. just create another folder for the project's valid branches only. On Sep 3, 5:55 am, n8gray wrote: > 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 wrote: > > > Hi Nathan, > > > Yeah, I often get problems with --ignore-pathstoo. 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.
[git-users] Re: git-svn: server-side madness has killed my buzz
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 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.
[git-users] Re: git-svn: server-side madness has killed my buzz
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 view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/rzMgUuqkd9YJ. 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.
