branch

Let's say I have an Eclipse Project which uses versioning control with EGit and is connected with a remote repository git@myrepo.com:git2013 . In my project, under the local branch newstuff , I create and change some files. Now, I want to push this to a remote branch named newstuff in my remote repository. But my remote repository only holds a branch master . How do I create a new remote branch called newstuff ? PS: Please do not answer with command-line git commands; describe how to do it in EGit. VonC You can follow the section " Configuring upstream push " in order to push a given branch:

Today I faced with one problem. My teammate created branch from master. He developed one feature in this branch and after that developed two subfeatures in subfeature's branches. At last he did two refactoring commit of the entire thing. So... C--D E--F | subfeatures / \ / \ B------M1------M2--G--H | feature / A-------------------K | master Usually we rebase feature branches before no-fast-forward merge it into master. But of course this rebase fails. Rebased feature branch became looking like: B'--C'--D'--E'--F'--G'--H' / A--K Of course pointers of C & D became wrong so I also get two

I run 'git branch -r' and get origin/branch1 origin/branch2 From the man page, the -r option will "list or delete (if used with -d) the remote-tracking branches". So origin/branch1 and origin/branch2 are known as remote-tracking branches. However, you can't commit directly onto a remote-tracking branch (an anonymous branch will be created instead). A remote-tracking branch simply tracks a remote branch when running 'git fetch'. Here's where the semantics get a little blurry for me. If I then git checkout -b branch1 origin/branch1 I get the following output: "Branch branch1 set up to track

I'd like to move my last few commits from master into a branch of their own. The tree on my PC looks like that: W (some branch) / X1--X2--X3--X4--Y--Z1--Z2 (master) I'd like it to look like: W (some branch) / X1--X2--X3--X4 (master) \ Y--Z1--Z2 (my new branch) However, the tree at GitHub looks like: W (some branch) / X1--X2--X3--X4--Y (master) That's what I saw as a solution for moving the last commits to another branch: git checkout master git branch my_new_branch git reset <commit_id> My question is: would I be able to successfully push to GitHub after moving the commits into a new branch

I'm getting my feet wet with git tagging, but my previous background is in Subversion, where "tags" were really just copies, not "real" tags... If I add a tag to a git repo, is it applied to all branches or only the current one? For example, if I currently have these branches ( git branch -v ): * master deadbeef My master head comment dev baddfeed My def head comment And the currently checked out branch is master, as you can see. Now suppose I git tag -a TAGNAME , does TAGNAME apply only to deadbeef (master branch) or to baddfeed (dev branch) as well? e.g., Say I subsequently switch to the dev