From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH 2/2] c/r: define s390-specific checkpoint-restart code (v5)
Date: Tue, 24 Feb 2009 15:49:27 -0600 [thread overview]
Message-ID: <20090224214927.GA29993@us.ibm.com> (raw)
In-Reply-To: <1235510471.26788.317.camel@nimitz>
Quoting Dave Hansen (dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org):
> On Tue, 2009-02-24 at 14:04 -0600, Serge E. Hallyn wrote:
> > OTOH I'm not eager to make such a change right now only to find
> > months later that there was a good reason to keep it in the hdr
> > after all :)
>
> The thing that bothers me about all of these things is that we can't
> truly evaluate them on their merits because we can't see how they are
> expected to be used in the future. Surely there are multiple ways we
> can implement details of the incremental checkpoint.
>
> -- Dave
Oh I think that was a bogus guess on my part anyway.
Like I say I don't want to encourage churn for the sake of churn
at this point, but you've got me thinking that moving parent into
the details and giving it a more useful name could *really*
dilute some of the mystery in these patches.
It's sounding good to me...
-serge
next prev parent reply other threads:[~2009-02-24 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 18:37 [PATCH 0/2] c/r: Add s390 support Dan Smith
[not found] ` <1235500639-9597-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-02-24 18:37 ` [PATCH 1/2] c/r: Add CR_COPY() macro Dan Smith
[not found] ` <1235500639-9597-2-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-02-24 19:20 ` Serge E. Hallyn
2009-02-24 18:37 ` [PATCH 2/2] c/r: define s390-specific checkpoint-restart code (v5) Dan Smith
[not found] ` <1235500639-9597-3-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-02-24 19:37 ` Serge E. Hallyn
[not found] ` <20090224193737.GB24007-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-02-24 19:46 ` Dave Hansen
2009-02-24 20:04 ` Serge E. Hallyn
[not found] ` <20090224200430.GA26259-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-02-24 21:21 ` Dave Hansen
2009-02-24 21:49 ` Serge E. Hallyn [this message]
2009-02-24 19:56 ` Dan Smith
[not found] ` <87k57flib8.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2009-02-24 20:09 ` Serge E. Hallyn
[not found] ` <20090224200939.GB26259-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-02-24 20:53 ` Dan Smith
2009-02-24 19:31 ` [PATCH 0/2] c/r: Add s390 support Dan Smith
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=20090224214927.GA29993@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=danms-r/Jw6+rmf7HQT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.