git remote add coworker git://path/to/coworkers/repo.git git fetch coworker git checkout –track coworker/foo This will setup a local branch foo, tracking the remote branch coworker/foo. So when your co-worker has made some changes, you can easily pull them: git checkout foo git pull Response to comments: Cool 🙂 And if I’d like to make my own … Read more
To avoid confusion, recent versions of git deprecate this somewhat ambiguous –set-upstream option in favor of a more verbose –set-upstream-to option with identical syntax and behavior. [ Reference ] git branch –set-upstream-to <remote-branch> sets the default remote branch for the current local branch. Any future git pull command (with the current local branch checked-out), will … Read more
In this case, using openssh over putty was key. Original answer (tips for debugging) I can log in via ssh with the git user. That means this works: ssh git@serverIp You do have a HOME variable defined, and ssh public/private keys (id_rsa / id_rsa.pub) in %HOME%/.ssh/. This question suggests a different url: git remote set-url … Read more
Yes and no. git remote update fetches from all remotes, not just one. Without looking at the code to see if remote update is just a shell script (possible) it, basically, runs fetch for each remote. git fetch can be much more granular.
I came to this question looking for an explanation about what the message “your branch is ahead by…” means, in the general scheme of git. There was no answer to that here, but since this question currently shows up at the top of Google when you search for the phrase “Your branch is ahead of … Read more
You can use git push -u <remote_name> <local_branch_name> to set the default upstream. See the documentation for git push for more details.
You’ve got the syntax for the scp-style way of specifying a repository slightly wrong – it has to be: [user@]host.xz:path/to/repo.git/ … as you can see in the git clone documentation. You should use instead the URL: [email protected]:/gittest.git i.e. in the URL you’re using, you missed out the : (colon) To update the URL for origin … Read more
You have your arguments to the remote add command reversed: git remote add <NAME> <PATH> So: git remote add bak /home/sas/dev/apps/smx/repo/bak/ontologybackend/.git See git remote –help for more information.
To avoid confusion, recent versions of git deprecate this somewhat ambiguous –set-upstream option in favor of a more verbose –set-upstream-to option with identical syntax and behavior. [ Reference ] git branch –set-upstream-to <remote-branch> sets the default remote branch for the current local branch. Any future git pull command (with the current local branch checked-out), will … Read more
You can git remote set-url origin new.git.url/here See git help remote. You also can edit .git/config and change the URLs there. You’re not in any danger of losing history unless you do something very silly (and if you’re worried, just make a copy of your repo, since your repo is your history.)