From: Thomas Gleixner <tglx@linutronix.de>
To: speck@linutronix.de
Subject: Re: Publishing the Speck archive
Date: Tue, 21 Aug 2018 14:08:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1808211406500.1535@nanos.tec.linutronix.de> (raw)
In-Reply-To: <1534848622.10027.46.camel@infradead.org>
On Tue, 21 Aug 2018, speck for David Woodhouse wrote:
> On Mon, 2018-08-20 at 15:42 -0700, speck for Dave Hansen wrote:
> > On 08/20/2018 02:30 AM, speck for Thomas Gleixner wrote:
> > >
> > > are there any objections to publishing the archive of this list now that
> > > L1TF is public?
> >
> > I don't *really* care strongly, but I was definitely a bit more candid
> > with what is normally NDA-like material for Intel on there than I would
> > have been for LKML.
>
> I was thinking the same thing. I can't think of specific examples but I
> definitely have a vague sense of having been more candid here than I
> would have been on a truly public list. Ironic really, since here my
> "competitors" are definitely paying attention :)
>
> I hate to say it... but is there really much benefit in the list
> archive? Who's really going to trawl through it and learn anything
> useful from the discussions we happened to have as we were thrashing it
> out?
In general I find it useful to get context of stuff and how it evolved and
why certain decisions were made when looking at code quite some time after
it got merged and everyone involved cleared memory, vanished from the
project etc.
Thanks,
tglx
prev parent reply other threads:[~2018-08-21 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 9:30 Publishing the Speck archive Thomas Gleixner
2018-08-20 22:42 ` [MODERATED] " Dave Hansen
2018-08-21 9:22 ` Thomas Gleixner
2018-08-21 10:50 ` [MODERATED] " David Woodhouse
2018-08-21 12:08 ` Thomas Gleixner [this message]
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.21.1808211406500.1535@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=speck@linutronix.de \
/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).