From: Alex Elder <aelder@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [GIT Review] xfs: 2.6.36 fixes
Date: Wed, 25 Aug 2010 21:17:26 -0500 [thread overview]
Message-ID: <1282789046.5543.2.camel@doink> (raw)
In-Reply-To: <20100825045032.GM31488@dastard>
On Wed, 2010-08-25 at 14:50 +1000, Dave Chinner wrote:
> On Wed, Aug 25, 2010 at 11:10:28AM +1000, Dave Chinner wrote:
> > On Tue, Aug 24, 2010 at 05:54:58PM -0500, Alex Elder wrote:
> > > On Tue, 2010-08-24 at 12:44 +1000, Dave Chinner wrote:
> > > > Folks,
> > > >
> > > > Can you please cast an eye over the the tree below to check that
all
> > > > the bug fixes that need to go into 2.6.36 are there? If so, I'll
> > > > send a pull request to Linus tomorrow.
> > > >
> > > > Note that these are just the outstanding bug fixes that have
been
> > > > reviewed (as Linus has again decreed for pull requests after
-rc1),
> > > > so it not the complete set of reviewd patches that exist.
> > > >
> > > > Cheers,
> > > >
> > > > Dave.
> > >
> > > All of these commits look good to me. I will have these
> > > and all the rest published on the oss.sgi.com tree later
> > > this week. I've been on vacation and have gotten behind.
> >
> > I'm going to send the pull to Linus, anyway, Alex.
> >
> > The problem is deeper than "been on vacation" - regardless of
> > whether you are on vacation we can't rely on you to do anything
> > immediately. It might be code review, triage community reported
> > bugs, pulling patches into the OSS tree or sending stuff to Linus,
> > but it's always a week or two later than it needs to be. This is
> > not a new problem, either.
>
> So this doesn't get taken the wrong way, this is not a comment on
> the quality of the work you do, Alex. My concern is the limited
> amount of time you have available to do the required work and
> avoiding the bottleneck it causes.
This has been an ongoing issue, and I concur that it's been a matter
of giving XFS maintenance the time and attention it requires.
In July I raised this issue internally and got agreement to give
this more priority versus other competing demands. That helped
some, but there still were some other things that needed my
dedicated focus, and that disrupted the continuity of my attention
to XFS maintenance.
My vacation last week, directly on the heels of my trip to Boston
the week before (during which I had limited network access) resulted
in an extended delay whose cause was actually pretty unusual (and
unfortunately timed).
I have now been directed to spend 100% of my time on XFS maintenance
for the community. This will not result in 10 minute turnaround but
it will allow me to offer everything I've got to the cause, without
interruption.
SGI continues to be committed to supporting XFS (for more than just
its own customers), and in the coming month or so is going to be
evaluating what more can be done to serve and benefit the community.
In the mean time XFS maintenance has my full attention.
-Alex
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-08-26 2:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 2:44 [GIT Review] xfs: 2.6.36 fixes Dave Chinner
2010-08-24 9:12 ` Christoph Hellwig
2010-08-24 22:54 ` Alex Elder
2010-08-25 1:10 ` Dave Chinner
2010-08-25 4:50 ` Dave Chinner
2010-08-26 2:17 ` Alex Elder [this message]
2010-08-26 4:13 ` Dave Chinner
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=1282789046.5543.2.camel@doink \
--to=aelder@sgi.com \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.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