xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Tim Deegan <tim@xen.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH] docs: Use lists.xen.org not lists.xensource.com
Date: Thu, 28 Jun 2012 09:11:42 +0100	[thread overview]
Message-ID: <20120628081142.GA32085@ocelot.phlegethon.org> (raw)
In-Reply-To: <bffb9db1332434164c44.1340869166@cosworth.uk.xensource.com>

At 08:39 +0100 on 28 Jun (1340872766), Ian Campbell wrote:
> # HG changeset patch
> # User Ian Campbell <ian.campbell@citrix.com>
> # Date 1340869061 -3600
> # Node ID bffb9db1332434164c444eb019e5ec6694529a72
> # Parent  6507f3b61e343d29cd04fb380282a5a039640874
> docs: Use lists.xen.org not lists.xensource.com
> 
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> 
> diff -r 6507f3b61e34 -r bffb9db13324 docs/man/xl.cfg.pod.5
> --- a/docs/man/xl.cfg.pod.5	Wed Jun 27 16:21:53 2012 +0100
> +++ b/docs/man/xl.cfg.pod.5	Thu Jun 28 08:37:41 2012 +0100
> @@ -1082,7 +1082,7 @@ XXX).  However all options are included 
>  fully documented.
>  
>  Patches to improve incomplete items (or any other item) would be
> -greatfully received on the xen-devel@lists.xensource.com mailing
> +greatfully received on the xen-devel@lists.xen.org mailing

May as well s/greatful/grateful/ while you're editing this line. :)
(and again below).

Cheers,

Tim.

>  list. Please see L<http://wiki.xen.org/wiki/SubmittingXenPatches> for
>  information on how to submit a patch to Xen.
>  
> diff -r 6507f3b61e34 -r bffb9db13324 docs/man/xl.pod.1
> --- a/docs/man/xl.pod.1	Wed Jun 27 16:21:53 2012 +0100
> +++ b/docs/man/xl.pod.1	Thu Jun 28 08:37:41 2012 +0100
> @@ -1255,5 +1255,5 @@ L<http://wiki.xen.org/wiki/Paravirt_Linu
>  
>  =head1 BUGS
>  
> -Send bugs to xen-devel@lists.xensource.com, see
> +Send bugs to xen-devel@lists.xen.org, see
>  http://wiki.xen.org/xenwiki/ReportingBugs on how to send bug reports.
> diff -r 6507f3b61e34 -r bffb9db13324 docs/man/xlcpupool.cfg.pod.5
> --- a/docs/man/xlcpupool.cfg.pod.5	Wed Jun 27 16:21:53 2012 +0100
> +++ b/docs/man/xlcpupool.cfg.pod.5	Thu Jun 28 08:37:41 2012 +0100
> @@ -111,7 +111,7 @@ XXX).  However all options are included 
>  fully documented.
>  
>  Patches to improve incomplete items (or any other item) would be
> -greatfully received on the xen-devel@lists.xensource.com mailing
> +greatfully received on the xen-devel@lists.xen.org mailing
>  list. Please see L<http://wiki.xen.org/wiki/SubmittingXenPatches> for
>  information on how to submit a patch to Xen.
>  
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2012-06-28  8:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28  7:39 [PATCH] docs: Use lists.xen.org not lists.xensource.com Ian Campbell
2012-06-28  8:11 ` Tim Deegan [this message]
2012-06-28 15:12   ` [PATCH] docs: Use lists.xen.org not lists.xensource.com [and 2 more messages] Ian Jackson
2012-06-28 15:13     ` Ian Campbell
2012-06-28  8:26 ` [PATCH] docs: Use lists.xen.org not lists.xensource.com Keir Fraser

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=20120628081142.GA32085@ocelot.phlegethon.org \
    --to=tim@xen.org \
    --cc=ian.campbell@citrix.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 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).