git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git
cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream
git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git
cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream
I used to think that
ssh -X [email protected]
"just bloody worked". However this might not work - ssh must play ball on both sides of the link. On the remote (ssh server, X client) sshd must sit behind some port, tell Xlib to send X11 requests to it and then forward them back to you the X server (where the ssh client is). If the remote box is locked down to prevent this, you will get:
X11 forwarding request failed on channel 0
as part of an otherwise working login. As it happens, I am the admin of the remote box in question, so I followed the ArchWiki and went to /etc/ssh/sshd_config and uncommented
| " ============================================================================= | |
| " Miller Medeiros .vimrc file | |
| " ----------------------------------------------------------------------------- | |
| " heavily inspired by: @factorylabs, @scrooloose, @nvie, @gf3, @bit-theory, ... | |
| " ============================================================================= | |
| " ----------------------------------------------------------------------------- | |
| " BEHAVIOR |