xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Juergen Gross <jgross@suse.com>
Cc: minios-devel@lists.xenproject.org,
	xen-devel@lists.xenproject.org, wei.liu2@citrix.com,
	samuel.thibault@ens-lyon.org
Subject: Re: [PATCH] minios: remove reference to xensource.com
Date: Tue, 29 Nov 2016 09:01:28 +0000	[thread overview]
Message-ID: <20161129090128.GP11640@citrix.com> (raw)
In-Reply-To: <20161125132029.16291-1-jgross@suse.com>

On Fri, Nov 25, 2016 at 02:20:29PM +0100, Juergen Gross wrote:
> include/xen/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>

Acked-by: Wei Liu <wei.liu2@citrix.com>

I will apply this when I'm done with 4.8 release.

> ---
>  include/xen/hvm/pvdrivers.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/xen/hvm/pvdrivers.h b/include/xen/hvm/pvdrivers.h
> index 77994d2..01ea2ae 100644
> --- a/include/xen/hvm/pvdrivers.h
> +++ b/include/xen/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
> -- 
> 2.10.0
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-11-29  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-25 13:20 [PATCH] minios: remove reference to xensource.com Juergen Gross
2016-11-29  9:01 ` Wei Liu [this message]
2016-12-03 16:07   ` Wei Liu

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=20161129090128.GP11640@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=jgross@suse.com \
    --cc=minios-devel@lists.xenproject.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=xen-devel@lists.xenproject.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 NNTP newsgroup(s).