I am not sure this is possible unless you have first tracked oll the branches from origin repo (see the SO question Track all remote git branches as local branches ) The other solution would be (not tested) to make a alias for: $ git pull refs/heads/*:refs/remotes/origin From git pull man page : The above specifies that all remote branches are tracked using tracking branches in refs/remotes/origin/ hierarchy under the same name.
I am not sure this is possible unless you have first tracked oll the branches from origin repo (see the SO question "Track all remote git branches as local branches") The other solution would be (not tested) to make a alias for: $ git pull refs/heads/*:refs/remotes/origin/* From git pull man page: The above specifies that all remote branches are tracked using tracking branches in refs/remotes/origin/ hierarchy under the same name.
All branches are tracked... They're just not set up to pull. – Sean Clark Hess Mar 18 '10 at 20:06 Ah, nevermind! My mistake.
I had one branch that was set up using git checkout -b somebranch origin/somebranch. The rest were created locally and pushed up. Thanks – Sean Clark Hess Mar 18 '10 at 20:12.
I use git checkout -b somebranch origin/somebranch to make sure my local branches track remotes already. I would like a way to pull from the tracked branch no matter which branch I am using. Is there a way to do this without putting an entry in the config file for each branch?
It would be difficult to maintain if we have to remember to manually enter some config stuff for each branch.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.