emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Paul Mead <paul.d.mead@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Using Git to update more than one machine (one without	network access)
Date: Wed, 25 Feb 2009 17:23:13 +0000 (UTC)	[thread overview]
Message-ID: <loom.20090225T172019-747@post.gmane.org> (raw)
In-Reply-To: 511.1235581813@gamaville.dokosmarshall.org

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
that may not be an option either.

> Also, it might be possible to use HTTP (presumably, you have an http
> proxy at work to get through the firewall) instead of the GIT protocol
> to do the pull, but I believe that depends on whether the repository has
> been set up properly to allow that - I have not tried it in the org
> case, but I was using it for the mainline Linux kernel before I had set
> up the SOCKS proxy service: it was slower but it worked.

That would be a nice solution, but I just tried using git clone
http://repo.or.cz/org-mode and it caused an error, so that doesn't seem to be a
working route, sadly.


  reply	other threads:[~2009-02-25 17:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 16:38 Using Git to update more than one machine (one without network access) Paul Mead
2009-02-25 16:58 ` David Thole
2009-02-25 17:12   ` Paul Mead
2009-02-25 17:10 ` Nick Dokos
2009-02-25 17:23   ` Paul Mead [this message]
2009-02-25 17:41 ` Ian Barton
2009-02-25 18:09   ` Paul Mead
2009-02-25 18:19   ` Paul Mead
2009-02-25 18:41     ` Bernt Hansen
2009-02-25 18:56       ` Paul Mead
2009-02-25 19:31         ` Bernt Hansen
2009-02-25 21:12           ` Paul Mead

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20090225T172019-747@post.gmane.org \
    --to=paul.d.mead@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).