Linux Container Development
 help / color / mirror / Atom feed
From: Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
To: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: linux-2.6-lxc ?
Date: Fri, 29 Aug 2008 15:59:43 +0200	[thread overview]
Message-ID: <48B800CF.7030206@fr.ibm.com> (raw)
In-Reply-To: <1219938246.5497.6.camel@nimitz>

Dave Hansen wrote:
> On Thu, 2008-08-28 at 17:03 +0200, Cedric Le Goater wrote:
>> what's in that git tree ?  
>>
>> 	http://git.kernel.org/?p=linux/kernel/git/daveh/linux-2.6-lxc.git;a=summary
>>
>> I'd like to start playing with some C/R code. Is that the one to use ? are 
>> oren patches included ? If not, can I help ? :)
> 
> Nope, they're not in there, yet.
> 
> Speaking of which, I should update that.
> 
> The best thing you could help with would be to try and find any little
> nuggets from what Oren is doing that can be simplified or pushed
> upstream, first.  Or those that require something done upstream first.
> Things where he copy-and-pasted code need to go first.

To start with, here's a version of oren's patchset for the latest mainline 
kernel :

	http://legoater.free.fr/patches/2.6.27/2.6.27-rc5-orenl-cr-v2/

I've fixed the patches and ckpt+rstr work as announced.

Now I'm looking at your own version :

	http://legoater.free.fr/patches/2.6.27/2.6.27-rc5-daveh-cr-v2/

and oren's to see how we can reorganize the bits and pieces.

Thanks,

C.

  reply	other threads:[~2008-08-29 13:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28 15:03 linux-2.6-lxc ? Cedric Le Goater
     [not found] ` <48B6BE55.3000901-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-08-28 15:44   ` Dave Hansen
2008-08-29 13:59     ` Cedric Le Goater [this message]
     [not found]       ` <48B800CF.7030206-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-08-31  6:36         ` Oren Laadan

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=48B800CF.7030206@fr.ibm.com \
    --to=clg-nmtc/0zbporqt0dzr+alfa@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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