From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Access to Buildroot git via https
Date: Wed, 27 Jul 2016 08:32:13 +0000 [thread overview]
Message-ID: <1469608243.6389.5.camel@synopsys.com> (raw)
In-Reply-To: <20160718104900.77748f2a@free-electrons.com>
Hi Thomas,
On Mon, 2016-07-18 at 10:49 +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Mon, 18 Jul 2016 08:44:00 +0000, Alexey Brodkin wrote:
>
> >
> > I'm wondering if there's a way to access Buildroot main git repo via HTTPS?
> > Here (https://git.busybox.net/buildroot/) it is mentioned only git protocol URL:
> > git://git.busybox.net/buildroot which doesn't work behind some corporate firewalls
> > (and I'm tired asking IT guys to open git port for each particular server IP).
> >
> > IMHO HTTPS option would be very convenient especially keeping in mind very few
> > people have rights to commit.
>
> It would indeed be useful. But in the mean time, you can already get
> Buildroot from https://, by using the Github mirror at
> https://github.com/buildroot/buildroot/. The Github mirror is updated
> every 10 minutes.
I just noticed GitHub repo was not updated in 10 days.
Is there a problem with it?
The last commit on GitHub is "directfb: depends on NPTL threading".
-Alexey
next prev parent reply other threads:[~2016-07-27 8:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 8:44 [Buildroot] Access to Buildroot git via https Alexey Brodkin
2016-07-18 8:49 ` Thomas Petazzoni
2016-07-18 8:50 ` Alexey Brodkin
2016-07-19 4:57 ` Bernd Kuhls
2016-07-27 8:32 ` Alexey Brodkin [this message]
2016-07-27 20:25 ` Thomas Petazzoni
2016-07-27 20:52 ` Peter Korsgaard
2016-07-27 21:31 ` Alexey Brodkin
2016-07-19 6:28 ` Yann E. MORIN
2016-07-19 7:13 ` Thomas Petazzoni
2016-07-19 9:15 ` Alexey Brodkin
2016-08-03 19:48 ` Peter Korsgaard
2016-08-04 3:59 ` Alexey Brodkin
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=1469608243.6389.5.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.