David Thole dthole at gmail.com writes:
Paul,
The way I've accomplished the task you're talking about is instead of
trying to push and pull *to* the work machine, I use another machine with
less restrictive firewalls to push and pull from. This is how I do it...
Work - Web Server -
Nick Dokos nicholas.dokos at hp.com writes:
There is another possibility that you might want to investigate: if
there is a SOCKS proxy server available at work, you can arrange to pass
git traffic through that.
Nice idea, sadly even the identity of the proxy server is hidden, so I guess
Ian Barton lists at manor-farm.org writes:
Use git clone to create a repo on your usb stick.
Pull changes from Carsten' git repo to your usb stick.
Pull changes from your usb stick to both your work and home computers.
In other words your usb stick is your own master repo.
It works!
Paul Mead paul.d.m...@gmail.com writes:
Ian Barton lists at manor-farm.org writes:
Use git clone to create a repo on your usb stick.
Pull changes from Carsten' git repo to your usb stick.
Pull changes from your usb stick to both your work and home computers.
In other words your usb
Paul Mead paul.d.m...@gmail.com writes:
Bernt Hansen bernt at norang.ca writes:
I suggest you put bare repositories on the USB stick.
...
$ git push # update any existing branches on the usb stick
On your work machine just clone the USB repo
$ git clone /path/to/usb/org-mode.git
Bernt Hansen bernt at norang.ca writes:
snip
to update the stick with those commits. At work you clone the stick
(once) and origin at work is the usb stick. Then you git fetch or git
pull at work to get commits from the usb stick as needed.
HTH,
-Bernt
Bernt, many thanks. I'll need to
