From: Allison Henderson <achender@vnet.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Allison Henderson <achender@linux.vnet.ibm.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: Fwd: [XFSTEST Add Fallocate Punch Hole Tests 1/3 v4] Add Punch Hole to FSX
Date: Mon, 06 Jun 2011 10:41:41 -0700 [thread overview]
Message-ID: <4DED1155.4060503@vnet.ibm.com> (raw)
In-Reply-To: <20110606150323.GB22236@infradead.org>
On 06/06/2011 08:03 AM, Christoph Hellwig wrote:
> Btw, you mails are basically unreadable to me. There doesn't seem to be
> any threading context, and they all have your reply on top with a full
> quote. Please try again with a submission from a saner mailer, and all
> important context information included in the [PATCH 0/n] mail.
Sorry about that, does this reply look better? I realized that I needed
to send the patch to more lists than just xfs, so I forwarded the set
and the discussions. I think the forwarding might have been what broke
the threading, and I can turn off the full quote. If this reply looks
ok, I can resend the set and just collapse down the questions into a
[PATCH 0/n] email. Thx!
WARNING: multiple messages have this Message-ID (diff)
From: Allison Henderson <achender@vnet.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
xfs-oss <xfs@oss.sgi.com>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Allison Henderson <achender@linux.vnet.ibm.com>
Subject: Re: Fwd: [XFSTEST Add Fallocate Punch Hole Tests 1/3 v4] Add Punch Hole to FSX
Date: Mon, 06 Jun 2011 10:41:41 -0700 [thread overview]
Message-ID: <4DED1155.4060503@vnet.ibm.com> (raw)
In-Reply-To: <20110606150323.GB22236@infradead.org>
On 06/06/2011 08:03 AM, Christoph Hellwig wrote:
> Btw, you mails are basically unreadable to me. There doesn't seem to be
> any threading context, and they all have your reply on top with a full
> quote. Please try again with a submission from a saner mailer, and all
> important context information included in the [PATCH 0/n] mail.
Sorry about that, does this reply look better? I realized that I needed
to send the patch to more lists than just xfs, so I forwarded the set
and the discussions. I think the forwarding might have been what broke
the threading, and I can turn off the full quote. If this reply looks
ok, I can resend the set and just collapse down the questions into a
[PATCH 0/n] email. Thx!
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-06-06 17:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 19:13 Fwd: [XFSTEST Add Fallocate Punch Hole Tests 1/3 v4] Add Punch Hole to FSX Allison Henderson
2011-06-03 19:13 ` Allison Henderson
2011-06-06 15:03 ` Christoph Hellwig
2011-06-06 15:03 ` Christoph Hellwig
2011-06-06 17:41 ` Allison Henderson [this message]
2011-06-06 17:41 ` Allison Henderson
2011-06-07 12:06 ` Christoph Hellwig
2011-06-07 12: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=4DED1155.4060503@vnet.ibm.com \
--to=achender@vnet.ibm.com \
--cc=achender@linux.vnet.ibm.com \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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 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.