From: Christoph Hellwig <hch@infradead.org>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-xfs@oss.sgi.com
Subject: Re: [patch 0/5] Patch queue for 2.6.29
Date: Tue, 9 Dec 2008 05:07:48 -0500 [thread overview]
Message-ID: <20081209100748.GA25897@infradead.org> (raw)
In-Reply-To: <200812091057.49292.Martin@lichtvoll.de>
On Tue, Dec 09, 2008 at 10:57:48AM +0100, Martin Steigerwald wrote:
> Am Dienstag 09 Dezember 2008 schrieb Christoph Hellwig:
> > These are my outstanding patches for 2.6.29. The first two have
> > already been rewied by Dave, the others still need review.
>
> Patch 4/5 appears to be missing.
It's now there for me, unfortunately the oss has some rather
non-deterministic delays..
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-12-09 10:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 9:47 [patch 0/5] Patch queue for 2.6.29 Christoph Hellwig
2008-12-09 9:47 ` [patch 1/5] replace b_fspriv with b_mount Christoph Hellwig
2008-12-09 9:56 ` Martin Steigerwald
2008-12-09 20:04 ` Russell Cattelan
2008-12-09 9:47 ` [patch 2/5] simplify projid check in xfs_rename Christoph Hellwig
2008-12-09 9:47 ` [patch 3/5] resync headers with libxfs Christoph Hellwig
2008-12-10 3:28 ` Lachlan McIlroy
2008-12-09 9:47 ` [patch 4/5] add a FMODE flag to make XFS invisible I/O less hacky Christoph Hellwig
2008-12-10 3:27 ` Lachlan McIlroy
2008-12-09 9:47 ` [patch 5/5] use inode_change_ok for setattr permission checking Christoph Hellwig
2008-12-10 3:40 ` Lachlan McIlroy
2008-12-10 5:09 ` Timothy Shimmin
2008-12-09 9:57 ` [patch 0/5] Patch queue for 2.6.29 Martin Steigerwald
2008-12-09 10:07 ` Christoph Hellwig [this message]
2008-12-09 11:02 ` Martin Steigerwald
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=20081209100748.GA25897@infradead.org \
--to=hch@infradead.org \
--cc=Martin@lichtvoll.de \
--cc=linux-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.