[Top] [All Lists]

Re: xfstest failures

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: xfstest failures
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 7 Nov 2013 04:23:28 -0800
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20131107115722.GB11434@dastard>
References: <20131106105451.GA31283@xxxxxxxxxxxxx> <20131106194417.GF6188@dastard> <20131107082234.GA30243@xxxxxxxxxxxxx> <20131107115722.GB11434@dastard>
User-agent: Mutt/1.5.21 (2010-09-15)
On Thu, Nov 07, 2013 at 10:57:22PM +1100, Dave Chinner wrote:
> However, Christoph, you should not have found this stuff given it's
> been almost 5 months since I sent patches to handle these cases.
> This is a perfect example of what is wrong with the way XFS is being
> maintained right now.

> That's the fundamental problem here.  When I change stuff, I can't
> get the maintainers to do anything with the code I post unless I put
> on my cranky pants and start shouting and making people cry. I hate
> having to do this, but it seems like it's the only thing that the
> maintainers respond to.
I've not seen them reposted either.  While review and commit latencie
can vary and be very high the most effective counter measure is frequent

<Prev in Thread] Current Thread [Next in Thread>