From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] GFS: update gfs-kernel HEAD to 2.6.20 (please review)
Date: Thu, 1 Feb 2007 11:44:34 -0600 [thread overview]
Message-ID: <20070201174434.GA23329@redhat.com> (raw)
In-Reply-To: <45C223D4.6060304@redhat.com>
On Thu, Feb 01, 2007 at 11:31:00AM -0600, Robert Peterson wrote:
> I'd also like to hear your opinions on if/when we should make HEAD deviate
> from RHEL5 and start tracking the upstream kernel rather than the RHEL5
Lacking the porting that you're doing is the only reason HEAD kernel bits
don't match the latest upstream. So, as soon as your patch is done and
works, check it in.
Dave
prev parent reply other threads:[~2007-02-01 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 17:31 [Cluster-devel] [PATCH] GFS: update gfs-kernel HEAD to 2.6.20 (please review) Robert Peterson
2007-02-01 17:44 ` David Teigland [this message]
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=20070201174434.GA23329@redhat.com \
--to=teigland@redhat.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.