From: Robert Schiele <rschiele@uni-mannheim.de>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
gcc@gcc.gnu.org, overseers@gcc.gnu.org, cvs-hackers@gnu.org
Subject: Re: cvs corrruption in gcc/unroll.c
Date: Sun, 09 Mar 2003 00:10:00 -0000 [thread overview]
Message-ID: <20030309000845.GA8185@schiele.local> (raw)
In-Reply-To: <Pine.BSF.4.44.0303081843270.11070-100000@dair.pair.com>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
On Sat, Mar 08, 2003 at 06:45:00PM -0500, Hans-Peter Nilsson wrote:
> On Sun, 9 Mar 2003, Robert Schiele wrote:
> > On Sat, Mar 08, 2003 at 01:58:01PM -0600, Michael Elizabeth Chastain wrote:
> > > I'm seeing CVS corruption in gcc/unroll.c.
> >
> > Yeah, not only there. It seems subversions is completely broken. I
> > hope, it is only subversions that is broken. Maybe someone wants to
> > resync the whole tree.
>
> Please contact the subversions people, whomever they are and
> tell them. (Thanks in advance.) AFAIK rsync is initiated from
> there, not from gcc.gnu.org.
Hmm, I also don't know, who is responsible for this cvs mirror. But
as cvs-hackers@gnu.org is the only mail address mentioned on the
subversions web server, I added this one to CC. Hope someone reads
this that feels responsible.
Otherwise all the anonymous cvs readers might switch back to the main
tree, which would be a pitty, because that would most likely lead to
enormous load problems there again, as we had before subversions was
the "official" anonymous cvs source.
Robert
--
Robert Schiele Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
[-- Attachment #2: Type: application/pgp-signature, Size: 481 bytes --]
next prev parent reply other threads:[~2003-03-09 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030308234157.GA30916@schiele.local>
2003-03-08 23:45 ` Hans-Peter Nilsson
2003-03-09 0:10 ` Robert Schiele [this message]
2003-03-09 0:19 ` Jason Molenda
2003-03-09 0:38 ` Robert Schiele
2003-03-09 2:55 ` Jason Molenda
2003-03-09 6:31 Michael Elizabeth Chastain
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=20030309000845.GA8185@schiele.local \
--to=rschiele@uni-mannheim.de \
--cc=cvs-hackers@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=hp@bitrange.com \
--cc=mec@shout.net \
--cc=overseers@gcc.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).