On Feb 20, 1:39 pm, Rob Wilkerson <r...@robwilkerson.org> wrote: > 1. Having cloned a current Svn repository ( git svn clone > -shttps://svn.mydomain.com/myproject/workingdirectory), I'm under the > assumption that it's pulled all of my branches and tags, but "git > branch" returns only "master". I'd like to be working on a branch that > exists in Svn (at branches/development/newfeature), but does not > appear to exist in my cloned repository. Am I missing something? > > 2. What is a "remote branch", exactly? I see references to local vs. > remote, but I don't understand how they're different from each other > in terms of behavior or my own interaction. I understand what the > works local and remote mean, just not sure how it applies here. I > assumed that cloning meant that everything became local. Hopefully > that makes sense.
So I'm learning more about branches and I think I've spotted at least part of the problem and maybe an inconsistency. I have a semi- standard branching and tagging structure. I have maintenance and dev branches along with build and release tags. For example: trunk/ branches/maintenance/ branches/maintenance/1.0.0 branches/maintenance/1.1.0 branches/development/ branches/development/feature1 branches/development/sandbox1 tags/build/ tags/build/v1.0.0.2909 tags/build/v1.0.0.3290 tags/build/v1.1.0.3337 tags/release/v1.0.0.3290 tags/release/v1.1.0.3337 You get the idea. These are representative rather than actual subdirectories and revision numbers. After cloning the entire repository, git seems to recognize the remote branches as: $ git branch -r development developm...@1340 maintenance maintena...@1340 tags/build tags/bu...@1340 tags/release tags/rele...@1340 trunk tr...@1340 Does git-svn just not branches subdirectories or is there a way that I can pull the "friendlier" branch names? What I'd like to see is development/feature1, development/sandbox1, maintenance/1.1.0, etc. Is there any way to make that happen? Thanks again. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
