From: Jonathan Corbet <corbet@lwn.net>
To: Luke Nowakowski-Krijger <lnowakow@eng.ucsd.edu>
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
pbonzini@redhat.com, rkrcmar@redhat.com, kvm@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] Documentation: kvm: Convert cpuid.txt to .rst
Date: Mon, 8 Jul 2019 14:20:32 -0600 [thread overview]
Message-ID: <20190708142032.4fbd175e@lwn.net> (raw)
In-Reply-To: <20190708201510.GA13296@luke-XPS-13>
On Mon, 8 Jul 2019 13:15:10 -0700
Luke Nowakowski-Krijger <lnowakow@eng.ucsd.edu> wrote:
> > > +:Author: Glauber Costa <glommer@redhat.com>, Red Hat Inc, 2010
> >
> > I rather suspect that email address doesn't work these days.
> >
>
> No I guess it wont :). We would still keep this correct?
There's nothing good that will come from keeping a broken email address
there. You could either:
- Just take the address out, or
- Track Glauber down and get a newer address; you could ask him about the
licensing while you're at it :)
Thanks,
jon
next prev parent reply other threads:[~2019-07-08 20:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 21:38 [PATCH 0/3] [PATCH 0/3] Documentation: virtual: convert files from .txt to Luke Nowakowski-Krijger
2019-07-06 21:38 ` [PATCH 1/3] Documentation: virtual: Add toctree hooks Luke Nowakowski-Krijger
2019-07-08 19:54 ` Jonathan Corbet
2019-07-08 20:28 ` Luke Nowakowski-Krijger
2019-07-06 21:38 ` [PATCH 2/3] Documentation: kvm: Convert cpuid.txt to .rst Luke Nowakowski-Krijger
2019-07-08 20:00 ` Jonathan Corbet
2019-07-08 20:15 ` Luke Nowakowski-Krijger
2019-07-08 20:20 ` Jonathan Corbet [this message]
2019-07-26 22:19 ` Paolo Bonzini
2019-07-06 21:38 ` [PATCH 3/3] Documentation: virtual: Convert paravirt_ops.txt " Luke Nowakowski-Krijger
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=20190708142032.4fbd175e@lwn.net \
--to=corbet@lwn.net \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lnowakow@eng.ucsd.edu \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.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).