From: "Frank Ch. Eigler" <fche@elastic.org>
To: "taylor, david" <david.taylor@emc.com>
Cc: "tromey@redhat.com" <tromey@redhat.com>,
"overseers@sourceware.org" <overseers@sourceware.org>
Subject: Re: access to binutils-gdb.git
Date: Wed, 20 Jan 2016 15:07:00 -0000 [thread overview]
Message-ID: <20160120150737.GP51204@elastic.org> (raw)
In-Reply-To: <63F1AEE13FAE864586D589C671A6E18B020952@MX203CL03.corp.emc.com>
Hi, David -
> [...] For months I updated a local clone of the binutils-gdb
> repository using the http protocol. And it worked. Recently it
> stopped working. [...] Forbidden You don't have permission to
> access /git/binutils-gdb.git/ on this server. [...]
I guess you don't have access to git: or ssh: instead?
We blacklist some IP address ranges due to a history of abuse. Do you
have any idea what the outgoing address of your connections might be?
- FChE
next prev parent reply other threads:[~2016-01-20 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 14:56 taylor, david
2016-01-20 15:07 ` Frank Ch. Eigler [this message]
2016-01-20 15:35 ` taylor, david
2016-04-11 15:43 Access " taylor, david
2016-04-11 15:51 ` Frank Ch. Eigler
2016-04-11 16:07 taylor, david
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=20160120150737.GP51204@elastic.org \
--to=fche@elastic.org \
--cc=david.taylor@emc.com \
--cc=overseers@sourceware.org \
--cc=tromey@redhat.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).