From: Petr Baudis <pasky@ucw.cz>
To: overseers@sourceware.org
Subject: Re: libc-hack policy
Date: Fri, 13 Nov 2009 18:23:00 -0000 [thread overview]
Message-ID: <20091113182320.GC12890@machine.or.cz> (raw)
In-Reply-To: <20091113165506.GB22412@ednor.casa.cgf.cx>
On Fri, Nov 13, 2009 at 11:55:06AM -0500, Christopher Faylor wrote:
> On Fri, Nov 13, 2009 at 04:00:00PM +0100, Petr Baudis wrote:
> >Is it possible to change libc-hack policy so that the subscription is
> >open to all but posting is still restricted to the same set of people
> >as now? Or is there a technical restriction that prevents this with
> >the current list software? (It's probably not a too big deal if it
> >isn't possible, but it would be good to have a clear picture here.)
>
> You're asking system administrators to change mailing list policy. We
> don't do that.
>
> Since Ulrich has indicated that he doesn't want to change the policy we
> won't be changing the policy.
I'm asking for input into ongoing discussion, where it was claimed by
Roland (who otherwise said "There is no reason not to allow read-only
subscriptions, sure--there are no secrets there, of course." and Carlos
suggested that I should ask you if it's technically possible, so I'm
just doing that...
--
Petr "Pasky" Baudis
A lot of people have my books on their bookshelves.
That's the problem, they need to read them. -- Don Knuth
next prev parent reply other threads:[~2009-11-13 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 15:00 Petr Baudis
2009-11-13 16:06 ` Ulrich Drepper
2009-11-13 16:55 ` Christopher Faylor
2009-11-13 18:23 ` Petr Baudis [this message]
2009-11-13 18:25 ` Ulrich Drepper
2009-12-11 1:34 ` sourceware.org shell access Petr Baudis
2009-12-11 2:11 ` Christopher Faylor
2009-12-12 0:04 ` Roland McGrath
2009-12-18 23:02 ` Petr Baudis
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=20091113182320.GC12890@machine.or.cz \
--to=pasky@ucw.cz \
--cc=overseers@sourceware.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).