From: "Frank Ch. Eigler" <fche@redhat.com>
To: Sourceware Overseers <overseers@sources.redhat.com>
Subject: Re: [Bug web/15652] gcc.gnu.org cvsweb download is broken
Date: Tue, 25 May 2004 20:13:00 -0000 [thread overview]
Message-ID: <20040525194236.GE10808@redhat.com> (raw)
In-Reply-To: <20040525191537.GA22632@coe.bosbc.com>
Hi, Chris -
> >While investigating this just a tad, it occurred to me that anoncvs
> >should not require such a huge membership list any more. [...]
>
> Search the overseers archives.
(Sorry, couldn't find anything relevant with a few search probes.)
> The locking doesn't work for uberbaum.
I am not familiar with uberbaum's intricacies, but does anoncvs have
to lock anything there? Are some directories accidentally just not
"chmod o+rx"?
- FChE
next prev parent reply other threads:[~2004-05-25 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040525184243.15652.fcusack@fcusack.com>
2004-05-25 19:42 ` pinskia at gcc dot gnu dot org
2004-05-25 20:04 ` Frank Ch. Eigler
2004-05-25 20:13 ` Christopher Faylor
2004-05-25 20:13 ` Frank Ch. Eigler [this message]
2004-05-27 1:03 ` pinskia at gcc dot gnu dot org
2004-05-27 15:56 ` ian at wasabisystems dot com
2004-06-18 7:48 ` fcusack at fcusack dot com
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=20040525194236.GE10808@redhat.com \
--to=fche@redhat.com \
--cc=overseers@sources.redhat.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).