From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Dave Chinner <david@fromorbit.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Theodore Tso <tytso@MIT.EDU>,
david@lang.hm, linux-kernel@vger.kernel.org
Subject: Re: XFS problem in 2.6.32
Date: Thu, 09 Jun 2011 09:22:02 +0200 [thread overview]
Message-ID: <4DF0749A.2040506@profihost.ag> (raw)
In-Reply-To: <20110609025742.GS32466@dastard>
> If you want someone to blame, then point the fingers at me, not
> RedHat or RedHat's processes - RedHat is not involved in the
> processes and decisions as to what fixes
> get backported into the community stable trees. How that is done
> is mainly dictated by available resources, which are generally
> scarce. We push bug fixes into the lastest kernel release, and if
> known to be needed for stable series they get pushed back via the
> stable queues.
I'm really sorry that my post goes that way. It was never my intention
to blame anybody for anything.
I just didn't know the things work and was just wondering that Redhat
had a fix which wasn't pushed back to vanilla 2.6.32. But i also didn't
know that the xfs codebase is totally different due to other backports.
I'm sorry.
Stefan
prev parent reply other threads:[~2011-06-09 7:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 12:46 XFS problem in 2.6.32 Stefan Priebe - Profihost AG
2011-06-07 13:36 ` Theodore Tso
2011-06-07 13:49 ` Stefan Priebe - Profihost AG
2011-06-07 19:45 ` david
2011-06-07 21:57 ` Stefan Priebe - Profihost AG
2011-06-07 22:05 ` david
2011-06-08 3:28 ` Theodore Tso
2011-06-08 7:05 ` Stefan Priebe - Profihost AG
2011-06-08 8:00 ` John Kacur
2011-06-08 13:38 ` Ted Ts'o
2011-06-08 14:16 ` Mike Snitzer
2011-06-08 18:50 ` Ted Ts'o
2011-06-08 21:01 ` Christoph Hellwig
2011-06-08 9:03 ` Alan Cox
2011-06-08 13:30 ` Steven Rostedt
2011-06-09 2:57 ` Dave Chinner
2011-06-09 7:22 ` Stefan Priebe - Profihost AG [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=4DF0749A.2040506@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=david@fromorbit.com \
--cc=david@lang.hm \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tytso@MIT.EDU \
/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.