From: pinskia@gmail.com
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
"Frank Ch. Eigler" <fche@elastic.org>,
Simon Marchi <simon.marchi@ericsson.com>,
Samuel Bronson <naesten@gmail.com>,
"gdb@sourceware.org" <gdb@sourceware.org>,
"overseers@sourceware.org" <overseers@sourceware.org>
Subject: Re: git clone through http
Date: Fri, 30 May 2014 15:21:00 -0000 [thread overview]
Message-ID: <17250C21-1ACC-40E0-BD31-A64C9CC9720F@gmail.com> (raw)
In-Reply-To: <E59706EF8DB1D147B15BECA3322E4BDC1C6554FB@eusaamb103.ericsson.se>
On May 30, 2014, at 8:10 AM, Marc Khouzam <marc.khouzam@ericsson.com> wrote:
>> -----Original Message-----
>> From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On
>> Behalf Of Joel Brobecker
>> Sent: Friday, May 30, 2014 11:00 AM
>> To: Frank Ch. Eigler
>> Cc: Simon Marchi; Samuel Bronson; gdb@sourceware.org;
>> overseers@sourceware.org
>> Subject: Re: git clone through http
>>
>>>>> 2. Somehow set up a "smart" web-based git server. [...] Choice 2
>>>>> is clearly more complicated and more httpd-specific, but also more
>>>>> efficient in most cases.
>>>
>>> We'll consider it, though an even easier thing we could do is stop
>>> promoting the http:// git URL.
>>
>> If we do, it would be interesting to know where that is. I double-checked
>> GDB's website, and it only references the "git" protocol.
>
> I am trying to use the http access to the GDB git repo because I want to run
> automated tests using the master branch using a Jenkins infrastructure.
> That Jenkins machine has to go through a proxy to access the internet and the
> proxy does not trigger when using the git protocol. So I was hoping to fall back
> on the http protocol.
What about doing a local mirror?
Thanks,
Andrew
>
> We've faced similar issues for eclipse projects and having an http access to
> the repos has proven useful.
>
> I found the reference to that http access here at the top of the page of the git repo:
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git
>
> Thanks
>
> Marc
>
next prev parent reply other threads:[~2014-05-30 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53876894.5020103@ericsson.com>
[not found] ` <87ha48dp55.fsf@naesten.mooo.com>
2014-05-30 14:38 ` Simon Marchi
2014-05-30 14:48 ` Joel Brobecker
2014-05-30 14:50 ` Frank Ch. Eigler
2014-05-30 15:00 ` Joel Brobecker
2014-05-30 15:10 ` Marc Khouzam
2014-05-30 15:21 ` pinskia [this message]
2014-05-30 15:32 ` Simon Marchi
2014-05-30 15:44 ` Joel Brobecker
2014-05-30 16:48 ` Simon Marchi
2014-05-30 16:53 ` Marc Khouzam
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17250C21-1ACC-40E0-BD31-A64C9CC9720F@gmail.com \
--to=pinskia@gmail.com \
--cc=brobecker@adacore.com \
--cc=fche@elastic.org \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=naesten@gmail.com \
--cc=overseers@sourceware.org \
--cc=simon.marchi@ericsson.com \
/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.
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).