From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com, burn@swtf.dyndns.org
Subject: Re: audit releases in recent RHEL releases (eg 6 and 7)
Date: Wed, 29 Jul 2015 08:09:53 -0400 [thread overview]
Message-ID: <12729657.YWHmqzP4VJ@x2> (raw)
In-Reply-To: <1438155839.26354.125.camel@swtf.swtf.dyndns.org>
On Wednesday, July 29, 2015 05:43:59 PM Burn Alting wrote:
> I know this more a question for Red Hat, but before I approach my local
> Red Hat rep, does anyone on the list know why RHEL6 only implements up
> to a version of 2.3.7 yet RHEL7 goes up to a version of 2.4.1.
Sure. The issue is that if I pushed 2.4.2 into rhel6 and you start using
features in it, then what happens when you upgrade to RHEL7? RHEL6 is ahead
and there will be feature regressions.
> Basically, I want to know if RHEL6 can accept some elements from the
> 2.4[.0] release if I ask really really reeeeeeeeeally nicely.
File a rebase RFE request through your support channel and that would be a
good start. Technically there is no reason why RHEL6 can't use 2.4, the ABI is
the same.
-Steve
next prev parent reply other threads:[~2015-07-29 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 7:43 audit releases in recent RHEL releases (eg 6 and 7) Burn Alting
2015-07-29 12:09 ` Steve Grubb [this message]
2015-07-29 12:16 ` Burn Alting
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=12729657.YWHmqzP4VJ@x2 \
--to=sgrubb@redhat.com \
--cc=burn@swtf.dyndns.org \
--cc=linux-audit@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).