public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Rod Stewart <stewart@lab43.org>
Cc: <gcc@gcc.gnu.org>, <gcc-patches@gcc.gnu.org>
Subject: PATCH for Re: Autobuild at NetWinder.org will be going away
Date: Sat, 15 Sep 2001 23:28:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.33.0109160826370.30673-100000@deneb.dbai.tuwien.ac.at> (raw)
In-Reply-To: <Pine.LNX.4.33.0109151912530.26569-100000@dystopia.lab43.org>

On Sat, 15 Sep 2001, Rod Stewart wrote:
> The autobuild system which does nightly builds of binutils, gcc, gdb, and
> glibc for i386-linux and armv{3,4}l-linux from netwinder.org will be going
> away (probably in the next week or two).

Thanks for the note.  I installed the following patch to account for this.

Gerald

Index: snapshots.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/snapshots.html,v
retrieving revision 1.7
diff -u -3 -p -r1.7 snapshots.html
--- snapshots.html	2001/09/13 07:17:23	1.7
+++ snapshots.html	2001/09/16 06:25:28
@@ -41,10 +41,6 @@ brik -C &lt; .brik</p>
 of our current development sources on a regular basis:</p>

 <ul>
-<li><a href=" http://www.netwinder.org/build/gcc.html" ;>
-    armv3l-unknown-linux-gnu, armv4l-unknown-linux-gnu, and
-    i386-unknown-linux-gnu</a> by
-    <a href=" http://www.rebel.com" ;>Rebel.com</a></li>
 <li><a href=" http://www.codesourcery.com/gcc-snapshots.html" ;>i686-pc-linux-gnu</a>
     by CodeSourcery.</li>
 </ul>

  reply	other threads:[~2001-09-15 23:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-15 16:30 Rod Stewart
2001-09-15 23:28 ` Gerald Pfeifer [this message]
2001-09-16 11:07 ` Joseph S. Myers
2001-09-17  9:06   ` Rod Stewart

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=Pine.BSF.4.33.0109160826370.30673-100000@deneb.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=stewart@lab43.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).