public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Brad Lucier <lucier@math.purdue.edu>
To: savannah-hackers@gnu.org
Cc: lucier@math.purdue.edu (Brad Lucier),
	dje@watson.ibm.com, gcc@gcc.gnu.org
Subject: Re: subversions.gnu.org not being updated (fwd)
Date: Thu, 10 Oct 2002 13:25:00 -0000	[thread overview]
Message-ID: <200210101949.g9AJniX25138@banach.math.purdue.edu> (raw)

David Edelsohn believes that you should be notified if there's a problem
with subversion.gnu.org not updating its cvs directories from gcc.gnu.org.
In fact, this doesn't seem to have been done for about two days for the
mainline development version of gcc.

Brad Lucier

Forwarded message:
> From dje@watson.ibm.com  Thu Oct 10 14:15:09 2002
> Message-Id: <200210101914.PAA31202@makai.watson.ibm.com>
> To: Brad Lucier <lucier@math.purdue.edu>
> cc: gcc@gcc.gnu.org, savannah-hackers@gnu.org
> Subject: Re: subversions.gnu.org not being updated 
> In-Reply-To: Message from Brad Lucier <lucier@math.purdue.edu> 
>    of "Thu, 10 Oct 2002 14:05:16 CDT." <200210101905.g9AJ5Gr24972@banach.math.purdue.edu> 
> Date: Thu, 10 Oct 2002 15:14:58 -0400
> From: David Edelsohn <dje@watson.ibm.com>
> 
> >>>>> Brad Lucier writes:
> 
> Brad> There have been some messages on this list about subversions.gnu.org
> Brad> not being updated in the past two days...
> 
> 	Has anyone notified the savannah-hackers mailinglist at the GNU
> Project for them to restore their GCC CVS mirror?
> 
> David
> 

             reply	other threads:[~2002-10-10 19:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 13:25 Brad Lucier [this message]
2002-10-11  5:04 ` Mathieu Roy
2002-10-11 10:01   ` Jeff Bailey
2002-10-13 11:23     ` Loic Dachary
2002-10-13 12:30       ` Fergus Henderson
2002-10-13 14:00         ` Loic Dachary
2002-10-15 14:51           ` Gerald Pfeifer
2002-10-15 17:49             ` Joseph S. Myers

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=200210101949.g9AJniX25138@banach.math.purdue.edu \
    --to=lucier@math.purdue.edu \
    --cc=dje@watson.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=savannah-hackers@gnu.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).