From: Xi Ruoyao <xry111@mengyan1223.wang>
To: "yilu@bupt.edu.cn" <yilu@bupt.edu.cn>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Anonymous read-only Git access
Date: Thu, 05 Mar 2020 06:33:00 -0000 [thread overview]
Message-ID: <457c9b90e8bbb07075a8a84826cc5042593f1545.camel@mengyan1223.wang> (raw)
In-Reply-To: <2020030513501429647012@bupt.edu.cn>+B438A40D8CE39356
On 2020-03-05 13:50 +0800, yilu@bupt.edu.cn wrote:
> Hi,everyone
> I want to get the GCC-10 source and I followed the instructions in
> https://gcc.gnu.org/git.html, however, the command
> git clone git://gcc.gnu.org/git/gcc.git SomeLocalDir
> cannot work.
> And I found I cannot connect https://gcc.gnu.org/git/gcc.git even without
> firewall(I'm in China). I got a 403 Forbidden
> "You don't have permission to access /git/gcc.git/ on this server."
> "Apache Server at gcc.gnu.org Port 443".
> What can I do in this situation?
I guess some guy in BUPT "attacked" gcc.gnu.org somehow (maybe unintentionally,
just playing or testing some software) and caused the entire IP segment to be
banned.
You should contact the administrator of gcc.gnu.org. In the meantime try
git clone https://mirrors.tuna.tsinghua.edu.cn/git/gcc.git
It would be very fast since this mirror is in your city :).
(OT: Several BUPT students commenced some unsported behavior in our programming
contests. So our online judge is also banning BUPT IP segments.)
--
Xi Ruoyao <xry111@mengyan1223.wang>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2020-03-05 6:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 5:50 yilu
2020-03-05 6:33 ` Kewen.Lin
2020-03-05 6:33 ` Xi Ruoyao [this message]
2020-03-05 6:48 ` Kewen.Lin
2020-03-05 7:03 ` Xi Ruoyao
2020-03-05 8:15 ` yilu
2020-03-05 7:31 ` Liu Hao
2020-03-05 8:12 ` yilu
[not found] <5e609336.1c69fb81.34afe.adbbSMTPIN_ADDED_BROKEN@mx.google.com>
2020-03-05 6:03 ` Dan Kegel
[not found] <5e609329.1c69fb81.2d3a0.47d1SMTPIN_ADDED_BROKEN@mx.google.com>
2020-03-05 9:14 ` Jonathan Wakely
2020-03-05 9:27 ` Jonathan Wakely
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=457c9b90e8bbb07075a8a84826cc5042593f1545.camel@mengyan1223.wang \
--to=xry111@mengyan1223.wang \
--cc=gcc-help@gcc.gnu.org \
--cc=yilu@bupt.edu.cn \
/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).