On 6 Jun 2009, at 14:08, Marius Vollmer wrote:
David Bremner <[email protected]> writes:Probably the command "git show-ref" does the right thing with those.Thanks! I made some changes to use it instead of trying to parse the output of git branch (which, of course, was a sin to begin with). I also changed how you select branches or other interesting refs in general: instead of origin/feature you now have to type (with completion help of course) feature (origin)And if you do switch to a remote branch, Magit offers to create a localtracking branch instead. The idea is that you only rarely switch to remote branches. It's more common to start working on a remote branch and then you need a local tracking branch for it. Thus, the name or a remote branch is more important than the name of the remote. This is true for me at least. We can add customization options, of course, if this is annoying for different workflows. Opinions?
Sounds good to me. However...This broke the listing of git-svn unpushed/unpulled commits: git-svn remotes were not detected by the regexps in magit-list-interesting- refs: I've attached a patch to fix this.
Note that one should not try switching to a git-svn remote branch then telling magit to create a local tracking branch, since magit would not do the right thing in that situation.
-Steve
0001-Fix-display-of-unpushed-unpulled-git-svn-patches.patch
Description: Binary data
