From: Joseph Myers <joseph@codesourcery.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
Carlos O'Donell <carlos@redhat.com>,
"Frank Ch. Eigler" <fche@elastic.org>, <overseers@sourceware.org>
Subject: Re: Overseers list should not be public
Date: Fri, 22 Sep 2017 17:24:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1709221721580.17667@digraph.polyomino.org.uk> (raw)
In-Reply-To: <5c418dcb-6553-8090-641f-208f94ca0113@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
On Fri, 22 Sep 2017, Florian Weimer wrote:
> On 09/22/2017 04:47 PM, Frank Ch. Eigler wrote:
> > It's for lots of things - but I don't recall anything embarrassing
> > there, come to think of it. The funny/sad/embarrassing parts were
> > people trying to censor mailing list archives of personal folly, and
> > we haven't had a request for that in some time (whew). Do you have
> > another type of example in mind?
>
> https://sourceware.org/ml/overseers/2017-q3/msg00071.html
>
> Posting passwords to public lists even if they are temporary is … strange.
I think posting a password here is just an ordinary mistake.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-09-22 17:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 8:14 Florian Weimer
2017-09-15 12:56 ` Frank Ch. Eigler
2017-09-22 14:32 ` Carlos O'Donell
2017-09-22 14:40 ` Joseph Myers
2017-09-22 15:06 ` Martin Sebor
2017-09-22 16:37 ` Carlos O'Donell
2017-09-22 16:41 ` Frank Ch. Eigler
2017-09-22 16:56 ` Carlos O'Donell
2017-09-22 17:14 ` Frank Ch. Eigler
2017-09-22 17:34 ` Carlos O'Donell
2017-10-31 16:03 ` Frank Ch. Eigler
2017-09-22 17:06 ` Joseph Myers
2017-09-22 14:47 ` Frank Ch. Eigler
2017-09-22 14:56 ` Carlos O'Donell
2017-09-22 17:15 ` Florian Weimer
2017-09-22 17:24 ` Joseph Myers [this message]
2017-09-22 17:32 ` Carlos O'Donell
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=alpine.DEB.2.20.1709221721580.17667@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=fche@elastic.org \
--cc=fche@redhat.com \
--cc=fweimer@redhat.com \
--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).