From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Juergen Gross <jgross@suse.com>, xen-devel@lists.xen.org
Cc: ian.jackson@eu.citrix.com, david.vrabel@citrix.com, jbeulich@suse.com
Subject: Re: [PATCH] xen: remove reference to xensource.com
Date: Fri, 25 Nov 2016 13:13:24 +0000 [thread overview]
Message-ID: <8a4a5624-d93f-4cc8-c59a-41607c4d076f@citrix.com> (raw)
In-Reply-To: <20161125131247.15736-1-jgross@suse.com>
On 25/11/16 13:12, Juergen Gross wrote:
> xen/include/public/hvm/pvdrivers.h contains a reference to
> xen-devel@lists.xensource.com. Replace it by the correct address
> xen-devel@lists.xenproject.org
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
> ---
> xen/include/public/hvm/pvdrivers.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/xen/include/public/hvm/pvdrivers.h b/xen/include/public/hvm/pvdrivers.h
> index 77994d2..01ea2ae 100644
> --- a/xen/include/public/hvm/pvdrivers.h
> +++ b/xen/include/public/hvm/pvdrivers.h
> @@ -28,7 +28,7 @@
> * This is the master registry of product numbers for
> * PV drivers.
> * If you need a new product number allocating, please
> - * post to xen-devel@lists.xensource.com. You should NOT use
> + * post to xen-devel@lists.xenproject.org. You should NOT use
> * a product number without allocating one.
> * If you maintain a separate versioning and distribution path
> * for PV drivers you should have a separate product number so
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-11-25 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 13:12 [PATCH] xen: remove reference to xensource.com Juergen Gross
2016-11-25 13:13 ` Andrew Cooper [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=8a4a5624-d93f-4cc8-c59a-41607c4d076f@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.