xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jason Long <hack3rcon@yahoo.com>
Cc: Geza Gemes <geza.gemes@gmail.com>, xen-devel@lists.xen.org
Subject: Re: Define a new Wiki part for Xen Project.
Date: Fri, 18 Nov 2016 16:41:47 -0500	[thread overview]
Message-ID: <20161118214147.GF8933@char.us.oracle.com> (raw)
In-Reply-To: <1017574238.3114419.1479501944748@mail.yahoo.com>

On Fri, Nov 18, 2016 at 08:45:44PM +0000, Jason Long wrote:
> Thank you.
> If you find amy book or other useful information then inform me.

About C?

I would recommend The C Programming Language by 
Brian W. Kernighan, Dennis M. Ritchie

> --------------------------------------------
> On Fri, 11/18/16, Geza Gemes <geza.gemes@gmail.com> wrote:
> 
>  Subject: Re: [Xen-devel] Define a new Wiki part for Xen Project.
>  To: xen-devel@lists.xen.org
>  Date: Friday, November 18, 2016, 7:22 AM
>  
>  On 11/18/2016 11:25 AM,
>  Jason Long wrote:
>  > Hello developers.
>  > I have a request and please let me know
>  your idea.
>  > Can Xen experts define a new
>  part on Wiki about Xen developing for beginners? I mean is
>  something like "
>  >
>  kernelnewbies.org" but for Xen. For example, say to
>  users which programming languages are necessary, which book
>  is good for learning those languages and which part of Xen
>  codes are good for start.
>  > I know it may
>  funny for someone here or smeone consider the questions like
>  it as Spam but be sure it help begginers and other users for
>  improve Xen and get involved to project.
>  > I like to hear developers idea.
>  >
>  > Thank you.
>  >
>  >
>  _______________________________________________
>  > Xen-devel mailing list
>  > Xen-devel@lists.xen.org
>  > https://lists.xen.org/xen-devel
>  
>  Hi,
>  
>  As a xennewby I definitely support your
>  idea!
>  
>  Cheers,
>  
>  Geza
>  
>  
>  _______________________________________________
>  Xen-devel mailing list
>  Xen-devel@lists.xen.org
>  https://lists.xen.org/xen-devel
>  
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel

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

  reply	other threads:[~2016-11-18 21:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1017574238.3114419.1479501944748.ref@mail.yahoo.com>
2016-11-18 20:45 ` Define a new Wiki part for Xen Project Jason Long
2016-11-18 21:41   ` Konrad Rzeszutek Wilk [this message]
2016-11-19  6:14     ` Geza Gemes
2016-11-19 10:14     ` Jason Long
     [not found] <1063884205.3100821.1479501808573.ref@mail.yahoo.com>
2016-11-18 20:43 ` Jason Long
     [not found] <1080308251.3102846.1479501778363.ref@mail.yahoo.com>
2016-11-18 20:42 ` Jason Long
     [not found] <873461065.2711285.1479464753475.ref@mail.yahoo.com>
2016-11-18 10:25 ` Jason Long
2016-11-18 15:22   ` Geza Gemes
2016-11-18 15:38     ` Konrad Rzeszutek Wilk
2016-11-18 15:54       ` Lars Kurth
2016-11-18 16:01         ` Geza Gemes
2016-11-18 18:35   ` Dario Faggioli
2016-11-19 10:15     ` Jason Long

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=20161118214147.GF8933@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=geza.gemes@gmail.com \
    --cc=hack3rcon@yahoo.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).