public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Theodore Tso <tytso@MIT.EDU>
Cc: david@lang.hm, linux-kernel@vger.kernel.org
Subject: Re: XFS problem in 2.6.32
Date: Wed, 08 Jun 2011 09:05:44 +0200	[thread overview]
Message-ID: <4DEF1F48.7040804@profihost.ag> (raw)
In-Reply-To: <C4F797E7-3B2F-4BAD-BF69-2182DEA775A5@mit.edu>

Hi Ted,

>
> Not all distributions will participate in the maintenance stable tree.  Red Hat for example is probably worried about people  (specifically, Oracle) taking their kernel expertise "for free" and bidding it against them.  So it doesn't surprise me that they aren't submitting patches to the stable tree.  After all, they would like you to purchase a support contract if you want to get high quality, supported kernel.   Why should they give that work away for free?  After all, their salaried developers have to get paid somehow.  Others will contribute work in the hopes that other people will also contribute fixes back, but of course nothing forces Red Hat to do this.
>
> The thing that you have to understand that this is all a volunteer effort, and a few of your messages sound like you are expecting people to do the work for you.   It doesn't work that way.  If you ask nicely, maybe one of the XFS developers will help you.  But please don't expect free support.  That will just annoy people.
i'm sorry this was never my intention. I'm no native speaker so it might 
be that my word selection was not perfect.

I quite understand that alle people are doing this for free or got paid 
by a company who have their own interests.

I just thought it would be important to make it public that there is a 
problem with XFS in the longterm stable kernel and that it would be 
really nice if someone can take a look at it.

Greets Stefan

  reply	other threads:[~2011-06-08  7:05 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 [this message]
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

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=4DEF1F48.7040804@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=david@lang.hm \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox