All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH 0/8] 2.6.17 merge additions
Date: Wed, 14 Feb 2007 15:56:28 +0000	[thread overview]
Message-ID: <45D33F3C.76E4.0078.0@novell.com> (raw)

Following will be a set of patches that adjust 2.6.17 merges we had done
differently in our internal tree, and that I think shouldn't get lost. There
is no particular ordering among them, so if any seems questionable, others
can still be applied.

Jan

             reply	other threads:[~2007-02-14 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 15:56 Jan Beulich [this message]
2007-03-02  9:05 ` [PATCH 0/8] 2.6.17 merge additions Jan Beulich
2007-03-02  9:19   ` Keir Fraser
2007-03-02  9:59     ` Jan Beulich
2007-03-02 11:17       ` 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=45D33F3C.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=xen-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.