All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	MaoXiaoyun <tinnycloud@hotmail.com>,
	linux-ext4@vger.kernel.org, jack@suse.cz,
	xen devel <xen-devel@lists.xensource.com>
Subject: Re: [Xen-devel] Re: [patch 1/1] ext4-fix-dirty-extent-when-origin-leaf-extent-reac.patch
Date: Wed, 28 Sep 2011 15:46:44 -0400	[thread overview]
Message-ID: <20110928194644.GC19250@thunk.org> (raw)
In-Reply-To: <4E836A47.80107@goop.org>

On Wed, Sep 28, 2011 at 11:41:11AM -0700, Jeremy Fitzhardinge wrote:
> Since kernel.org 2.6.32 is still considered to be a maintained
> long-term-stable kernel, I keep the xen.git version up-to-date with
> stable-2.6.32 bugfixes and occasional separate Xen-specific fixes.  But
> I'd really prefer to avoid having any non-Xen private changes in that
> tree, in favour of getting everything from upstream stable.
> 
> Do you not consider it worth continuing support of the 2.6.32 stable
> tree with respect to ext4?

I just don't have the *time* to maintain backports of ext4 fixes to
2.6.32.  There have been so many bug fixes to ext4, and some of them
depend on changes in the quota subsystem, so trying to back port them
all would be hellish, and not something I'm willing to do on a
volunteer basis.

I'm busy enough with silly things like trying to help with the
kernel.org getting back on-line, that channelling my stay-really-late
hours to support users who are too cheap to pay distro support fees is
not really a way that I would choose to spend my personal time.

If someone would like to volunteer to be unpaid distro support, that's
great.  It's worth it as long as I get to volunteer somebody else's
time.  :-)

					- Ted


      reply	other threads:[~2011-09-28 19:46 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-06  7:24 ext4 BUG in dom0 Kernel 2.6.32.36 MaoXiaoyun
2011-09-06  7:24 ` MaoXiaoyun
2011-09-06 11:33 ` MaoXiaoyun
2011-09-06 11:33   ` MaoXiaoyun
2011-09-06 14:53 ` Konrad Rzeszutek Wilk
2011-09-06 15:11   ` MaoXiaoyun
2011-09-06 15:11     ` MaoXiaoyun
2011-09-06 18:55     ` [Xen-devel] " Jeremy Fitzhardinge
2011-09-07  2:35       ` MaoXiaoyun
2011-09-07  2:35         ` MaoXiaoyun
2011-09-16  6:08         ` MaoXiaoyun
2011-09-16  6:08           ` MaoXiaoyun
2011-09-25  8:45           ` [patch 1/1] ext4-fix-dirty-extent-when-origin-leaf-extent-reac.patch MaoXiaoyun
2011-09-25  8:45             ` MaoXiaoyun
2011-09-26 14:28             ` Konrad Rzeszutek Wilk
2011-09-27  2:22               ` MaoXiaoyun
2011-09-27  2:22                 ` MaoXiaoyun
2011-09-27  9:09                 ` [Xen-devel] " Jan Beulich
2011-09-27  9:09                   ` Jan Beulich
2011-09-27  9:54                   ` Tao Ma
2011-09-27 19:35               ` Ted Ts'o
2011-09-27 23:41                 ` Olivier B.
2011-09-28 12:47                   ` Konrad Rzeszutek Wilk
2011-09-28  4:09                 ` MaoXiaoyun
2011-09-28  4:09                   ` MaoXiaoyun
2011-09-28 10:45                 ` [PATCH] ext4: fix BUG_ON() in ext4_ext_insert_extent() Tao Ma
2011-10-27  9:43                   ` Ted Ts'o
2011-10-27 11:53                     ` Greg KH
2011-10-28  2:36                       ` Zheng Liu
2011-10-28  5:24                         ` Greg KH
2011-10-28  8:46                           ` Zheng Liu
2011-10-28  9:07                             ` Greg KH
2011-10-28 12:34                               ` [PATCH] ext4: fix BUG_ON() in ext4_ext_insert_extent() for .32 longterm Zheng Liu
2011-11-02 21:00                                 ` Greg KH
2011-11-03  3:06                                   ` Zheng Liu
2011-11-03 17:42                                     ` Greg KH
2011-10-28 12:36                               ` [PATCH] ext4: fix BUG_ON() in ext4_ext_insert_extent() for .33 longterm Zheng Liu
2011-09-28 18:41                 ` [Xen-devel] Re: [patch 1/1] ext4-fix-dirty-extent-when-origin-leaf-extent-reac.patch Jeremy Fitzhardinge
2011-09-28 19:46                   ` Ted Ts'o [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=20110928194644.GC19250@thunk.org \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tinnycloud@hotmail.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.