Hi Eric,
That also works. I don't think you even need the --track. The only
thing to remember is that if you are on one branch and do a git pull,
all the remote branches will be fetched, but only the branch you are
on will be updated to the remote copy.
so if there were changes in the remote d
Thanks Luuk,
This answers my question.
- Eric
On Apr 23, 12:58 am, Luuk Paulussen wrote:
> Hi Eric,
> You should be able to do:
>
> git fetch origin #This should fetch all remote refs, including the
> remote origin/dij without updating anything locally.
> git checkout -b dij origin/dij #this
Hi Eric,
You should be able to do:
git fetch origin #This should fetch all remote refs, including the
remote origin/dij without updating anything locally.
git checkout -b dij origin/dij #this will create a local branch
called dij to track origin/dij
To reverse the effects of your initial pull,
Hi Dan,
Thanks for replying to me.
Here is what I get from my home computer:
$ git branch -a
* master
network
origin/master
origin/network
As you can see, there is nothing about the "dij" branch that is remote
and that is
But this is what I get from the computer at the lab:
$ git branch
Hi Eric,
This is off the top of my head so hopefully someone can correct me if I've
made a mistake. Since you've merged the dij branch in with master, you
should already have the origin/dij remote branch. You need to create a
local tracking branch however to work on.
Verify that you have the re
