<https://lh5.googleusercontent.com/-nLGqgIZW_OQ/T_Rc3zfpBQI/AAAAAAAAAX4/eBmz41iDViw/s1600/Bildschirmfoto+2012-07-04+um+17.06.22.png> I found the mistake - i did not use double quotes when pushing the new branch
instead of " git push origin iss3168 " I have to use " git push origin "iss3168" " Then the new branch gets actually pushed into the remote rep. One thing I got aware of when I looked at the github network view it looks like iss3168 was branched off master - but it should be branched off update-2.0.2. Is it due to the lack of the github graph creation or do I have to wait until I merge iss3168 back to the update-2.0.2 branch? Am Mittwoch, 4. Juli 2012 16:52:53 UTC+2 schrieb Kersten Broich: > > I'm not sure where you got this -b switch from, but in my Git that is an >> invalid argument to git remote. What version of Git are you using? >> >> > I am sorry - What I meant to write was git branch -r > > How exactly do you try pushing this new issue branch ("#3178")? Please >> copy and paste in the exact commands you used. > > > OK! Thanks for helping me out - > > I am on a local git rep - update-2.0.2 - and I will start working on a new > branch which is related to a particular issue of my issue tracking system. > For reasons of convenience and overview we decided with the other team > members to name our branches with the same number as the issue id. > > So I start with "git checkout -b #3168" > > and before I do any kind of changes I try to push this new branch into my > remote origin repository. Whenever I try that I get the message "Everything > up-to-date". > > git push origin #3168 > > In the meantime I am not sure how much all this has to do with Xcode - as > there are some other strange behaviour - for example I can't rename my > branches. When I do a > > git branch -m #3168 iss3168 > > it just returns a listing of my branches but doesn't change anything at > all. > > I am running git version 126.96.36.199 (Apple Git-26) > > > > Am Mittwoch, 4. Juli 2012 10:07:50 UTC+2 schrieb Thomas Ferris Nicolaisen: >> >> On Tuesday, July 3, 2012 1:32:41 PM UTC+2, Kersten Broich wrote: >>> >>> I am having trouble understanding the concept of git local and remote >>> versioning. For example I have a iPhone app in a local git rep. Initally >>> this was my master branch. >>> >>> I then checked out a new branch git checkout -b "update-2.0.1". >>> >>> Then I set git push origin update-2.0.1 to ensure that I have a >>> seperate branch for developing this app update and when done merge it back >>> into my master branch. Fine! >>> >>> Now that I am on my update-branch I want to create branches for every >>> issue ID. So I say git checkout -b "#3178" - when I now try to push >>> this new issue-branch in my remote repository git says >>> "Everything-up-to-date". >>> >> >> How exactly do you try pushing this new issue branch ("#3178")? Please >> copy and paste in the exact commands you used. >> >> I don't see why it is not possible to push this issue branch to the >>> remote repository? >>> >>> git remote -b returns >>> >> >> I'm not sure where you got this -b switch from, but in my Git that is an >> invalid argument to git remote. What version of Git are you using? >> >> >>> I would love to see a third branch >>> >>> origin/update-2.0.1/#3178 >>> >>> >> >> This should work, although if you want to actually follow that naming >> convention, you should name your branches with the update-2.0.1/ prefix >> like this: >> >> git checkout -b "update-2.0.1/#3178" >> git push origin "update-2.0.1/#3178" >> >> There will then be a remote branch like this: >> >> git branch -a >> remotes/origin/update-2.0.1/#3178 >> >> Using hashes (#) in branch names is a bit cumbersome as the branch name >> has to be quoted like I do above (at least in my zsh), but it works. >> >>> -- 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/-/LNYL8NBA0QgJ. To post to this group, send email to email@example.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.