From: James Bulpin <james@xensource.com>
To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
xen-ia64-devel@lists.xensource.com
Subject: Re: Ownership of machine pages: Was: Essay on an important Xen decision (long)
Date: Thu, 12 Jan 2006 17:41:00 +0000 [thread overview]
Message-ID: <43C694AC.30804@xensource.com> (raw)
In-Reply-To: <516F50407E01324991DD6D07B0531AD590320E@cacexc12.americas.cpqcorp.net>
Magenheimer, Dan (HP Labs Fort Collins) wrote:
> (Sorry again for the late and off-thread reply... even though
> your message is addressed to me personally, to xen-devel,
> and to xen-ia64-devel, I didn't get a copy and just saw it
> in xen-devel which I only receive digested. Some strangeness
> in the mailing list nodupe feature maybe? James cc'ed....)
If you were on the recipient list of the original mail from Keir then
that should have gone directly to you without passing anywhere near the
list server, if you didn't get that then it's a problem with mail
servers at your or Keir's end. If you've got nodupe set for
xen-ia64-devel then your address being on the message means that you
won't get the message via the list. You still get the message on the
xen-devel digest because nodupe doesn't apply (or make sense) to digests.
Cheers,
James
next prev parent reply other threads:[~2006-01-12 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 14:50 Ownership of machine pages: Was: Essay on an important Xen decision (long) Magenheimer, Dan (HP Labs Fort Collins)
2006-01-12 17:41 ` James Bulpin [this message]
2006-01-13 4:03 ` Jayesh Salvi
-- strict thread matches above, loose matches on Subject: below --
2006-01-13 17:06 Magenheimer, Dan (HP Labs Fort Collins)
2006-01-11 22:49 Magenheimer, Dan (HP Labs Fort Collins)
2006-01-11 22:57 ` 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=43C694AC.30804@xensource.com \
--to=james@xensource.com \
--cc=dan.magenheimer@hp.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
/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.