From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: tes@sgi.com, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [GIT PULL] XFS update for 2.6.24-rc1
Date: Wed, 17 Oct 2007 13:50:34 -0700 [thread overview]
Message-ID: <20071017135034.0f8cc3bf.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071017203658.GA22073@infradead.org>
On Wed, 17 Oct 2007 21:36:58 +0100
Christoph Hellwig <hch@infradead.org> wrote:
> On Wed, Oct 17, 2007 at 09:03:39PM +1000, Tim Shimmin wrote:
> > Hi Linus,
> >
> > Please pull from the for-linus branch:
> > git pull git://oss.sgi.com:8090/xfs/xfs-2.6.git for-linus
> >
> > These include changes we have had scheduled for 2.6.24.
> > In particular they include Christoph's (hch's) behavior removal patches.
>
> Can you please send my '[PATCH] cleanup fid types mess' to Linus aswell?
> I have a stack of 15 patches reworking the nfs exporting code waiting
> in -mm to get in in this merge window that depend on this cleanup to
> free struct fid for generic useage.
>
> Also getting the makefile cleanup into mainline to reduce spurious difference
> would help a lot.
argh, -mm's *new-export*.patch has a dependency upon git-xfs's
ef6567a363c5f301c0bc885068d93cd9b3c05cc9. I never knew that, but I would
have found out later today...
Tim, if you want I can just steal that diff out of the xfs tree and send it
in separately.
next prev parent reply other threads:[~2007-10-17 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 11:03 [GIT PULL] XFS update for 2.6.24-rc1 Tim Shimmin
2007-10-17 20:36 ` Christoph Hellwig
2007-10-17 20:50 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-19 8:30 Tim Shimmin
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=20071017135034.0f8cc3bf.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tes@sgi.com \
--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