From: Rich Johnston <rjohnston@sgi.com>
To: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: stop special casing nfs and udf
Date: Tue, 3 Dec 2013 07:35:41 -0600 [thread overview]
Message-ID: <529DDE2D.3000501@sgi.com> (raw)
In-Reply-To: <20131203042936.GY8803@dastard>
On 12/02/2013 10:29 PM, Dave Chinner wrote:
> On Mon, Dec 02, 2013 at 05:36:30PM -0600, Ben Myers wrote:
>> On Tue, Dec 03, 2013 at 10:25:49AM +1100, Dave Chinner wrote:
>>> On Mon, Dec 02, 2013 at 09:40:45AM -0800, Christoph Hellwig wrote:
>>>> On Fri, Nov 22, 2013 at 01:15:53AM -0800, Christoph Hellwig wrote:
>>>>> ping?
>>>>
>>>> ping^2?
>>>
>>> I just got write access to the XFS git repos on oss.sgi.com, so I'll
>>> start hoovering up all the outstanding xfstests patches as a
>>> shakedown pass before I touch anything else...
>>
>> You might want to chat with Rich. There may be some already in progress.
>
> I've already pushed the ones I found last week on the list.
>
Thanks for doing this.
> FYI, I've been waiting for repo write perms to be able to push them
> since wednesday last week. Rich hasn't said anything on the mailing
> list or on IRC in that time, so I can only conclude that he's off
> doing something else.
>
> Handling xfstests patches in a manner necessary for upstream commit
> is something I've already integrated into my day-to-day workflow. As
> such, I'm able to push reviewed patches at almost any time (within
> reason - next day is best for everyone) at almost zero cost to me.
> That cost will go down as I script and optimise my workflow.
>
> If other developers don't want me to do this, let them speak up.
>
> However, as a maintainer, I'm not happy with leaving reviewed
> patches on the list for weeks before commiting them. As a developer,
> there is nothing more frsutrating that having to continually remind
> the maintainer that they need to commit a patch.
>
> Hence if a developer sends a ping to remind the maintainers about a
> reviewed patch that has been sitting around, then I'm going to do
> something about it straight away...
My apologies to Christoph. I missed that I thought he was waiting for a
review, not a commit from me.
>
> Cheers,
>
> Dave.
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-03 13:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 20:46 [PATCH] xfstests: stop special casing nfs and udf Christoph Hellwig
2013-11-12 17:35 ` Christoph Hellwig
2013-11-12 18:18 ` Eric Sandeen
2013-11-12 18:23 ` Eric Sandeen
2013-11-12 20:13 ` Jan Kara
2013-11-14 13:43 ` Christoph Hellwig
2013-11-12 18:32 ` Christoph Hellwig
2013-11-14 18:53 ` Eric Sandeen
2013-11-22 9:15 ` Christoph Hellwig
2013-12-02 17:40 ` Christoph Hellwig
2013-12-02 23:25 ` Dave Chinner
2013-12-02 23:36 ` Ben Myers
2013-12-03 4:29 ` Dave Chinner
2013-12-03 13:35 ` Rich Johnston [this message]
2013-12-03 23:30 ` Dave Chinner
2013-12-06 6:59 ` Stanislav Kholmanskikh
2013-12-06 16:06 ` Christoph Hellwig
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=529DDE2D.3000501@sgi.com \
--to=rjohnston@sgi.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