From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Andrew Pinski <pinskia@gmail.com>,
Siddhesh Poyarekar <siddhesh@gotplt.org>
Subject: Re: The GNU Toolchain Infrastructure Project
Date: Sun, 2 Oct 2022 23:56:36 +0200 [thread overview]
Message-ID: <YzoJFPiPU5rvyDNu@wildebeest.org> (raw)
In-Reply-To: <18919068-9af7-8a8b-9ea4-19e2035d6d78@gotplt.org>
Hi,
On Fri, Sep 30, 2022 at 11:51:03AM -0400, Siddhesh Poyarekar via Overseers wrote:
> On 2022-09-30 11:05, Andrew Pinski wrote:
> > > The overseers
> > > archives too AFAICT were made public only recently and I only happened
> > > to discover it last week.
> >
> > The archives have been public (or rather semi-public) for over 10
> > years now. It might not have been linked from anywhere but they have
> > existed for a long time now and have been public for that while too.
> > I am sorry you didn't know about the archives before; but that is on you.
>
> Funny that you call it semi-public (whatever that means) and then also say
> that it's on me that I didn't find the archives. FWIW, I've deliberately
> looked for the archives in the past and not found it. In any case, we
> digress.
You are both right. The overseers archives have always been publicly
archived (and go back to 1998), but till we setup public-inbox they
were not publicly advertised:
https://inbox.sourceware.org/overseers/YwJuV4e0I01sWxi0@wildebeest.org/
This was in part because we also handle account request on
overseers. It felt like a good idea to not make it easy for search
engines archive those. We now have a new (private, not archived)
account-requests list for that.
Cheers,
Mark
next prev parent reply other threads:[~2022-10-02 21:56 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 19:59 Carlos O'Donell
2022-09-28 14:06 ` Frank Ch. Eigler
2022-09-29 9:51 ` Mark Wielaard
2022-09-29 14:45 ` Jonathan Corbet
2022-09-29 17:13 ` Joseph Myers
2022-09-29 18:40 ` Elena Zannoni
2022-09-29 18:54 ` Andrew Pinski
2022-10-19 5:47 ` Carlos O'Donell
2022-09-29 21:13 ` Andrew Pinski
2022-09-30 14:35 ` Siddhesh Poyarekar
2022-09-30 15:05 ` Andrew Pinski
2022-09-30 15:51 ` Siddhesh Poyarekar
2022-10-02 21:56 ` Mark Wielaard [this message]
2022-09-30 15:22 ` Christopher Faylor
2022-09-30 15:34 ` Siddhesh Poyarekar
2022-10-02 21:38 ` Mark Wielaard
2022-10-02 22:19 ` Mark Wielaard
[not found] <d9cb6cf9-89f5-87bb-933b-a03240479e71@redhat.com>
[not found] ` <a9396df3-5699-46ef-0b33-6c7589274654@redhat.com>
2022-10-02 20:47 ` Mark Wielaard
2022-10-04 13:46 ` Siddhesh Poyarekar
2022-10-04 14:01 ` Frank Ch. Eigler
2022-10-04 14:13 ` Siddhesh Poyarekar
2022-10-04 14:19 ` Frank Ch. Eigler
2022-10-04 14:33 ` Siddhesh Poyarekar
2022-10-04 14:41 ` Frank Ch. Eigler
2022-10-04 14:55 ` Siddhesh Poyarekar
2022-10-04 15:07 ` Frank Ch. Eigler
2022-10-06 21:42 ` Alexandre Oliva
2022-10-04 17:10 ` Christopher Faylor
2022-10-04 17:17 ` Siddhesh Poyarekar
2022-10-04 18:42 ` Christopher Faylor
2022-10-04 19:05 ` Mark Wielaard
2022-10-04 19:10 ` Siddhesh Poyarekar
2022-10-06 20:02 ` Mark Wielaard
2022-10-06 20:12 ` Christopher Faylor
2022-10-06 21:37 ` Siddhesh Poyarekar
2022-10-07 13:39 ` Mark Wielaard
2022-10-06 21:07 ` Siddhesh Poyarekar
2022-10-06 21:36 ` Frank Ch. Eigler
2022-10-06 21:44 ` Siddhesh Poyarekar
2022-10-06 22:57 ` Frank Ch. Eigler
2022-10-11 13:02 ` Siddhesh Poyarekar
2022-10-07 8:57 ` Mark Wielaard
2022-10-11 13:24 ` Siddhesh Poyarekar
2022-10-11 14:23 ` Frank Ch. Eigler
2022-10-11 15:58 ` Alexandre Oliva
2022-10-11 17:14 ` David Edelsohn
2022-10-11 18:12 ` Frank Ch. Eigler
2022-10-12 8:00 ` Mark Wielaard
2022-10-12 13:18 ` Florian Weimer
2022-10-12 21:23 ` Mark Wielaard
2022-10-12 15:15 ` Jonathan Corbet
2022-10-12 10:55 ` Alexandre Oliva
[not found] <b00dc0aa-31a6-a004-a430-099af3d0f6d1@redhat.com>
[not found] ` <558996ac-e4a0-cf77-48b9-f7d0e13862e8@redhat.com>
2022-10-02 20:54 ` Mark Wielaard
2022-10-03 19:24 ` 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=YzoJFPiPU5rvyDNu@wildebeest.org \
--to=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=pinskia@gmail.com \
--cc=siddhesh@gotplt.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).