From: Dave Chinner <david@fromorbit.com>
To: Mark Tinguely <tinguely@sgi.com>
Cc: hch@infradead.org, xfs@oss.sgi.com
Subject: Re: xfsprogs patches pw 2883, 2986-2997
Date: Tue, 20 Dec 2011 13:33:43 +1100 [thread overview]
Message-ID: <20111220023343.GU23662@dastard> (raw)
In-Reply-To: <4EEFC18F.4020705@sgi.com>
On Mon, Dec 19, 2011 at 04:58:23PM -0600, Mark Tinguely wrote:
> Just a FYI to let you know that I testing your xfsprog patches that
> you submitted on Dec 2. I looked at the comments and the patches.
> The xfstests running now.
>
> Dave Chinner had feedback requests on a couple items.
Yes, but Christoph has already replied so all I'm waiting on is a
repost of the series from him addressing those comments. He did say
it might take a while as he had other more critical stuff to do.
> Below is my summary of the patches:
I'd prefer it if you don't send emails this way - there's no context
to your comments about each patch. I'd have to go to a web browser
to start patchworks and look up some random index number and read
stuff before coming back to my email to comment sanely. That's way
to much stuffing about for me to bother - there's no way I can chew
through a couple of thousand emails a day with that sort of
workflow.
It is much better to reply in line to each of the patch emails with
your comments. It is easy to understand the context of your
comments, you don't need to summarise all the patches (just reply to
ones you have comments about), and it fits the workflow we use for
tracking such comments (like patchworks). It also helps finding all
the discussion about a patch series in the mail archives. If you've
got a general comment about a series (like this email), reply to the
zero patch (the summary email).
Realistically, patchworks is just a tool to help the maintainer -
Ben - keep track of stuff if he requires help. It was set up because
Alex found it useful for this purpose, but if Ben doesn't need it
then it's probably not going to be maintained. Ben can weigh in on
this, though.....
FWIW, we talk quite a bit about bugs, patches, review and dev work
in #xfs (there's 50 people in the channel at the moment), so what
you see on the mailing list is often not the entire picture. There's
a lot more day to day dev stuff go on there - what you see on the
mailing list is often the end result of something that was first
discussed on #xfs. :)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-12-20 2:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 22:58 xfsprogs patches pw 2883, 2986-2997 Mark Tinguely
2011-12-20 2:33 ` Dave Chinner [this message]
2011-12-20 20:44 ` 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=20111220023343.GU23662@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=tinguely@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