From: Eric Sandeen <sandeen@sandeen.net>
To: Lachlan McIlroy <lachlan@sgi.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
xfs@oss.sgi.com, akpm@linux-foundation.org
Subject: Re: [GIT PULL] XFS update for 2.6.27
Date: Wed, 30 Jul 2008 23:09:33 -0500 [thread overview]
Message-ID: <48913AFD.9050407@sandeen.net> (raw)
In-Reply-To: <20080731025328.6328358C4C3F@chook.melbourne.sgi.com>
Lachlan McIlroy wrote:
...
> Eric Sandeen (3):
> [XFS]
> [XFS] Pack some shortform dir2 structures for the ARM old ABI
> [XFS] Disable queue flag test in barrier check.
Lachlan, you might want to fix up that blank summary as well?
Thanks,
-Eric
next prev parent reply other threads:[~2008-07-31 4:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 2:53 [GIT PULL] XFS update for 2.6.27 Lachlan McIlroy
2008-07-31 3:49 ` Dave Chinner
2008-07-31 4:59 ` Lachlan McIlroy
2008-08-01 19:02 ` Christoph Hellwig
2008-07-31 4:09 ` Eric Sandeen [this message]
2008-07-31 5:11 ` Lachlan McIlroy
2008-07-31 5:36 ` Lachlan McIlroy
-- strict thread matches above, loose matches on Subject: below --
2008-09-18 7:58 Lachlan McIlroy
2008-09-26 5:52 Lachlan McIlroy
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=48913AFD.9050407@sandeen.net \
--to=sandeen@sandeen.net \
--cc=akpm@linux-foundation.org \
--cc=lachlan@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox