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/-/UEm6KgsRIZIJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/git-users?hl=en.
