From: Carlos O'Donell <carlos_odonell@mentor.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: <overseers@sourceware.org>
Subject: Re: Banned IP address for CI glibc builds?
Date: Thu, 31 May 2012 20:22:00 -0000 [thread overview]
Message-ID: <4FC7B567.2090605@mentor.com> (raw)
In-Reply-To: <20120531173558.GG26201@redhat.com>
On 5/31/2012 1:35 PM, Frank Ch. Eigler wrote:
> Hi -
>
> On Thu, May 31, 2012 at 01:27:52PM -0400, Carlos O'Donell wrote:
>> One of our volunteers is bringing up a continuous integration system
>> for building and testing GLIBC.
>>
>> The IP address of the machine is: 130.161.158.181
>
> OK, it's been unblocked. Please ensure that these folks use efficient
> git operations (pull as opposed to clone).
Many thanks.
The volunteer says he uses `git pull --rebase` to update the repo which seems like the most efficient operation.
Cheers,
Carlos.
--
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos_odonell@mentor.com
carlos@codesourcery.com
+1 (613) 963 1026
next prev parent reply other threads:[~2012-05-31 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 18:08 Carlos O'Donell
2012-05-31 18:16 ` Frank Ch. Eigler
2012-05-31 20:22 ` Carlos O'Donell [this message]
2012-06-07 5:51 ` Jonathan Larmour
2012-05-31 20:24 ` Hans-Peter Nilsson
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=4FC7B567.2090605@mentor.com \
--to=carlos_odonell@mentor.com \
--cc=fche@redhat.com \
--cc=overseers@sourceware.org \
/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).