From: Konrad Rzeszutek Wilk <konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Lars Kurth <lars.kurth-LM2mM/qkH7s@public.gmane.org>
Cc: xen-arm-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org,
"xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org"
<xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>,
"xen-users-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org"
<xen-users-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>,
"xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org"
<xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>
Subject: Re: Another Xen Doc Day, Nov 29 or Dec 12
Date: Fri, 11 Nov 2011 10:00:14 -0500 [thread overview]
Message-ID: <20111111150013.GA4712@phenom.dumpdata.com> (raw)
In-Reply-To: <4EBD03EA.9070907-LM2mM/qkH7s@public.gmane.org>
On Fri, Nov 11, 2011 at 11:15:54AM +0000, Lars Kurth wrote:
> Hi,
>
> Given that the last Xen Document day was a real success, I wanted to
> propose another Xen Document day. Ideas of what to work on:
> - Continue some of the work stared by the dev community (more man
> pages, etc.)
> - Clean up pages in the new Wiki
> - I am also happy to be on stand-by to help anybody who wants to
> know how to use the new Wiki effectively
>
> Please vote on date preferences by voting
> +1 <your preferred date>
+1 Nov 29
next prev parent reply other threads:[~2011-11-11 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 11:15 Another Xen Doc Day, Nov 29 or Dec 12 Lars Kurth
[not found] ` <4EBD03EA.9070907-LM2mM/qkH7s@public.gmane.org>
2011-11-11 15:00 ` Konrad Rzeszutek Wilk [this message]
2011-11-15 13:25 ` Re: [Xen-API] " Andrew Eross
[not found] ` <CAL_tfFeUsDO1oAoKeWHLBJG0CHDf8A19mvjNX+zJCXfVdmfd3w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-16 15:59 ` [Xen-users] " Lars Kurth
[not found] ` <4EC3DDCE.9020506-LM2mM/qkH7s@public.gmane.org>
2011-11-24 16:13 ` Lars Kurth
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=20111111150013.GA4712@phenom.dumpdata.com \
--to=konrad.wilk-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=lars.kurth-LM2mM/qkH7s@public.gmane.org \
--cc=xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
--cc=xen-arm-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
--cc=xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
--cc=xen-users-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.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).