From: Dias Badekas <dbadekas@aia.gr>
To: emacs-orgmode@gnu.org
Cc: Bernt Hansen <bernt@norang.ca>
Subject: Re: problems cloning using the http protocol
Date: Wed, 15 Jul 2009 14:55:53 +0300 [thread overview]
Message-ID: <87ab365fee.fsf@aia00627.aia.gr> (raw)
In-Reply-To: <87y6qri3pc.fsf@gollum.intra.norang.ca> (Bernt Hansen's message of "Tue, 14 Jul 2009 13:17:51 -0400")
If this is relevant your question, you may want to look into setting up
a http CONNECT proxy, to use the efficient git protocol through your
corporate proxy.
I found these articles while searching for my problem.
http://www.emilsit.net/blog/archives/how-to-use-the-git-protocol-through-a-http-connect-proxy/
http://limlian.blogspot.com/2008/08/use-http-proxy-for-git-client.html
Bernt Hansen <bernt@norang.ca> writes:
> Scot Becker <scot.becker@gmail.com> writes:
>
>
>> So I don't think the problem is on the server end. Did you try any
>> other projects (using git+http proxy)?
>>
>> I don't suppose anyone knows how to git org develpment releases
>> sometimes behind an http proxy and sometimes directly (as on a laptop
>> that is sometimes behind a firewall, and sometimes not.) I couldn't
>> make this to work.
>
> There are multiple options
> ------------------------------------------------------------------------
> UNTESTED
>
> You might be able to get away with creating a second remote for the
> project like this:
>
> [remote "origin"]
> fetch = +refs/heads/*:refs/remotes/origin/*
> url = http://repo.or.cz/r/org-mode.git
>
> [remote "origin2"]
> url = git://repo.or.cz/org-mode.git
> fetch = +refs/heads/*:refs/remotes/origin/*
>
> then
>
> git fetch origin
> uses the HTTP protocol
>
> and
>
> git fetch origin2
> uses the git protocol
>
> You can set up origin to be whichever you use more often (or switch as
> required.) The only differences between these remotes are:
>
> - name of the remote - you can name it anything you like
> - the fetch = lines are identical - using the same remote ref
> 'refs/remotes/origin'. This should work okay since the repos are
> physically the same
> - the url specifies the transport method to use.
>
> ------------------------------------------------------------------------
>
> Just use two remotes
>
> origin for your fast git protocol access
> http for your slow http protocol access
>
> then you'll have remotes like origin/master and http/master
>
> If you can't git pull origin, you can manually git fetch http and git
> merge http/master or whatever is appropriate
>
> ------------------------------------------------------------------------
>
> I carry my org-mode.git around on my USB stick -- so I can just
> clone/pull/fetch from that without internet access. I'll update my
> workstation/laptop repo when it has net access and then push to the usb
> stick.
>
> HTH,
> Bernt
next prev parent reply other threads:[~2009-07-15 11:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 11:06 problems cloning using the http protocol Dias Badekas
2009-07-14 12:28 ` Scot Becker
2009-07-14 13:26 ` Nick Dokos
2009-07-14 13:27 ` Scot Becker
2009-07-14 17:17 ` Bernt Hansen
2009-07-14 20:22 ` Scot Becker
2009-07-15 11:55 ` Dias Badekas [this message]
2009-07-15 11:46 ` Dias Badekas
2009-07-14 13:27 ` Giovanni Ridolfi
2009-07-14 17:06 ` Richard Riley
2009-07-15 7:43 ` Giovanni Ridolfi
2009-07-16 20:58 ` Bastien
2009-07-15 8:49 ` Dias Badekas
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=87ab365fee.fsf@aia00627.aia.gr \
--to=dbadekas@aia.gr \
--cc=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).