From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] servers unavailable
Date: Wed, 13 Jul 2016 15:49:35 +0200 [thread overview]
Message-ID: <20160713154935.625340f7@free-electrons.com> (raw)
In-Reply-To: <CA+TH9VkBy3_krEK-buHDxhMq_ooYLA=HODWovLjeFvpZ6M=zEg@mail.gmail.com>
Hello,
On Wed, 13 Jul 2016 15:26:45 +0200, Angelo Compagnucci wrote:
> Since buildroot has a github account, why keep the website outside?!
> Github offers github pages with custom domain and protected against
> ddos attacks (and many more attack vectors).
> And why use a custom git server? We can always switch off pull
> requests and issues and keep the patch flow going as it goes now if we
> switch to github.
I am also starting to think we should switch to use github. We could
also use the Github issue tracker, since http://bugs.busybox.net/ is
down as well.
How does one disable pull requests in a Github project? This is clearly
one aspect where I (and I believe most of the core developers) prefer
the mailing list based review than the Web-based review for pull
requests.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-13 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 11:18 [Buildroot] servers unavailable Vlad Zakharov
2016-07-13 11:58 ` Yann E. MORIN
2016-07-13 12:23 ` Peter Korsgaard
2016-07-13 13:26 ` Angelo Compagnucci
2016-07-13 13:49 ` Thomas Petazzoni [this message]
2016-07-13 14:14 ` James Knight
2016-07-13 14:19 ` Angelo Compagnucci
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=20160713154935.625340f7@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox