From: Laszlo Ersek <lersek@redhat.com>
To: edk2-devel-01 <edk2-devel@ml01.01.org>,
qemu devel list <qemu-devel@nongnu.org>
Cc: Michael Tsirkin <mtsirkin@redhat.com>,
Josh Triplett <josh@joshtriplett.org>,
"Moore, Robert" <robert.moore@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Smith, Jonathan D" <jonathan.d.smith@intel.com>,
Shannon Zhao <zhaoshenglong@huawei.com>,
Marcel Apfelbaum <marcel@redhat.com>,
Igor Mammedov <imammedo@redhat.com>, Jake Edge <jake@lwn.net>
Subject: Re: [Qemu-devel] "Using Python to investigate EFI and ACPI"
Date: Thu, 3 Sep 2015 11:41:57 +0200 [thread overview]
Message-ID: <55E815E5.5030904@redhat.com> (raw)
In-Reply-To: <55E80FF8.10200@redhat.com>
Side point:
On 09/03/15 11:16, Laszlo Ersek wrote:
>
> I just found the LWN.net article with the title in the subject:
>
> http://lwn.net/SubscriberLink/655992/04701db2bbb7e716/
>
> ("Thank you LWN", of course. :))
I've just been advised in private, well-meaningly, that I shouldn't post
LWN Subscriber Links publicly.
I did that consciously. The notice on LWN's Subscriber Link generator
page is *not* lost on me; however, Jonathan Corbet has previously
publicly approved such *occasional* posting:
https://www.reddit.com/r/linux/comments/2lfhh8/kdbus_meets_linuxkernel_lwnnet/clumuze
I thought making this one article publicly readable "early" was (a)
basis for this discussion, (b) showcasing the value of LWN's journalism
(ie. "advertisment").
Thanks
Laszlo
next prev parent reply other threads:[~2015-09-03 9:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 9:16 [Qemu-devel] "Using Python to investigate EFI and ACPI" Laszlo Ersek
2015-09-03 9:41 ` Laszlo Ersek [this message]
2015-09-03 14:48 ` Jake Edge
2015-09-03 14:50 ` Josh Triplett
2015-09-03 15:22 ` josh
2015-09-03 15:53 ` Laszlo Ersek
2015-09-03 15:57 ` Moore, Robert
2015-09-03 16:16 ` Laszlo Ersek
2015-09-03 16:19 ` Moore, Robert
2015-09-03 16:41 ` josh
2015-09-03 17:19 ` Laszlo Ersek
2015-09-03 21:25 ` josh
2015-09-03 23:21 ` Laszlo Ersek
2015-09-04 17:11 ` josh
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=55E815E5.5030904@redhat.com \
--to=lersek@redhat.com \
--cc=edk2-devel@ml01.01.org \
--cc=imammedo@redhat.com \
--cc=jake@lwn.net \
--cc=jonathan.d.smith@intel.com \
--cc=josh@joshtriplett.org \
--cc=marcel@redhat.com \
--cc=mtsirkin@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robert.moore@intel.com \
--cc=zhaoshenglong@huawei.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 NNTP newsgroup(s).