From: Robert Schiele <rschiele@uni-mannheim.de>
To: Jason Molenda <jason-gcclist@molenda.com>
Cc: Hans-Peter Nilsson <hp@bitrange.com>,
Michael Elizabeth Chastain <mec@shout.net>,
overseers@gcc.gnu.org, cvs-hackers@gnu.org
Subject: Re: cvs corrruption in gcc/unroll.c
Date: Sun, 09 Mar 2003 00:38:00 -0000 [thread overview]
Message-ID: <20030309003635.GA7691@schiele.local> (raw)
In-Reply-To: <20030308162034.A94777@molenda.com>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
On Sat, Mar 08, 2003 at 04:20:34PM -0800, Jason Molenda wrote:
> Just to confirm - the subversions.gnu.org mirror of the gcc repository
> is done entirely from the subversions.gnu.org side. Unless the problem
> exists on gcc.gnu.org, or rsync is dishing out bad data, there isn't
> anything we can do from here.
I understand that. But as
:pserver:anoncvs@subversions.gnu.org:/cvsroot/gcc is mentioned on
http://gcc.gnu.org/cvs.html for "official" cvs anonymous read access
without any special contact address, this mailing list seems to be the
canonical place to discuss problems with this service in the hope that
the operators of the service are also reading this list. Otherwise a
contact address should also be given on http://gcc.gnu.org/cvs.html.
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:38 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
2003-03-09 0:19 ` Jason Molenda
2003-03-09 0:38 ` Robert Schiele [this message]
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=20030309003635.GA7691@schiele.local \
--to=rschiele@uni-mannheim.de \
--cc=cvs-hackers@gnu.org \
--cc=hp@bitrange.com \
--cc=jason-gcclist@molenda.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).