From: Bart Veer <bartv@redhat.com>
To: kingdon@redhat.com
Cc: overseers@sourceware.cygnus.com
Subject: Re: ftp load
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <200003151128.LAA28747@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <200003142156.QAA22288@devserv.devel.redhat.com>
>>>>> "Jim" == Jim Kingdon <kingdon@redhat.com> writes:
<snip>
>> As for long term plans, there has been talk of co-locating
>> sourceware, but it hasn't progressed beyond "just talk" yet.
Jim> I haven't heard anything about that in months. As far as I
Jim> know, we'd need to justify the $$$ if we want more bandwidth
Jim> and we haven't really been trying to do that recently (nor
Jim> did we have much luck when we - Donnie Barnes specifically -
Jim> did try. Speaking of which Donnie is at the Red Hat Center
Jim> for Open Source and we should probably hit them up for money
Jim> if/when we have a plan for what we need it for).
For whatever it is worth, I raised this with my manager yesterday to
try to get some progress. If enough people do so it might have some
effect. Possibly.
Bart
WARNING: multiple messages have this Message-ID
From: Bart Veer <bartv@redhat.com>
To: kingdon@redhat.com
Cc: overseers@sourceware.cygnus.com
Subject: Re: ftp load
Date: Wed, 15 Mar 2000 03:29:00 -0000 [thread overview]
Message-ID: <200003151128.LAA28747@sheesh.cygnus.co.uk> (raw)
Message-ID: <20000315032900.W5bYKViw3QF8UXqu6xRKC0yBfcjcuGfLdh6BbBJKPpc@z> (raw)
In-Reply-To: <200003142156.QAA22288@devserv.devel.redhat.com>
>>>>> "Jim" == Jim Kingdon <kingdon@redhat.com> writes:
<snip>
>> As for long term plans, there has been talk of co-locating
>> sourceware, but it hasn't progressed beyond "just talk" yet.
Jim> I haven't heard anything about that in months. As far as I
Jim> know, we'd need to justify the $$$ if we want more bandwidth
Jim> and we haven't really been trying to do that recently (nor
Jim> did we have much luck when we - Donnie Barnes specifically -
Jim> did try. Speaking of which Donnie is at the Red Hat Center
Jim> for Open Source and we should probably hit them up for money
Jim> if/when we have a plan for what we need it for).
For whatever it is worth, I raised this with my manager yesterday to
try to get some progress. If enough people do so it might have some
effect. Possibly.
Bart
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Stan Shebs
2000-03-14 8:32 ` Stan Shebs
2000-12-30 6:08 ` Jeffrey A Law
2000-03-14 8:45 ` Jeffrey A Law
2000-12-30 6:08 ` Mark Galassi
2000-03-14 10:43 ` Mark Galassi
2000-12-30 6:08 ` Chris Faylor
2000-03-14 9:35 ` Chris Faylor
2000-12-30 6:08 ` Bart Veer
2000-03-14 9:42 ` Bart Veer
2000-12-30 6:08 ` Jim Kingdon
2000-03-14 13:56 ` Jim Kingdon
2000-12-30 6:08 ` Jason Molenda
2000-03-14 14:20 ` Jason Molenda
2000-12-30 6:08 ` Bart Veer [this message]
2000-03-15 3:29 ` Bart Veer
2000-12-30 6:08 ` Chris Faylor
2000-03-15 5:38 ` Chris Faylor
2000-12-30 6:08 ` Jim Kingdon
2000-03-15 6:26 ` Jim Kingdon
2000-12-30 6:08 ` Chris Faylor
2000-03-15 6:30 ` Chris Faylor
2000-12-30 6:08 ` Jim Kingdon
2000-03-15 6:46 ` Jim Kingdon
2000-12-30 6:08 ` Chris Faylor
2000-03-15 7:00 ` Chris Faylor
2000-12-30 6:08 Louis Stone-Collonge
2000-03-21 22:14 ` Louis Stone-Collonge
2000-12-30 6:08 ` Jim Kingdon
2000-03-22 6:49 ` Jim Kingdon
2000-12-30 6:08 ` Stan Shebs
2000-03-23 8:32 ` Stan Shebs
2000-12-30 6:08 ` 'Chris Faylor'
2000-03-21 22:17 ` 'Chris Faylor'
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=200003151128.LAA28747@sheesh.cygnus.co.uk \
--to=bartv@redhat.com \
--cc=kingdon@redhat.com \
--cc=overseers@sourceware.cygnus.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).