Re: BUG or FEATURE? Use of '/' in branch names

implies that what I tried should work. In which case, how it's been *implemented* seems to be breaking the promise of the functional specification (if you view the documentation as such). Keith On 05/02/2014 03:16 PM, Jonathan Nieder wrote: > Hi Keith, > > Keith Derrick wrote:

BUG or FEATURE? Use of '/' in branch names

According to https://www.kernel.org/pub/software/scm/git/docs/git-check-ref-format.html a '/' is character to use in a branch name. git imposes the following rules on how references are named: 1. They can include slash / for hierarchical (directory) grouping, but no slash-separated component c

BUG: check-ref-format and rev-parse can not handle branches with an @ in their name combined with @{u}

if you have the branch checked out, then using HEAD instead of the branch name works > $git checkout @mybranch > Switched to branch '@mybranch' > Your branch is up-to-date with 'origin/master'. > $git check-ref-format --branch HEAD@{u} > origin/master > $git