From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com, linux-next@vger.kernel.org
Subject: Re: new xfs git tree
Date: Mon, 26 Jan 2009 22:41:30 -0800 [thread overview]
Message-ID: <20090126224130.53949fda.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090119011601.GA14708@infradead.org>
On Sun, 18 Jan 2009 20:16:01 -0500 Christoph Hellwig <hch@infradead.org> wrote:
> git://git.kernel.org/pub/scm/fs/xfs/xfs.git has all the fixes the
> have been peer-reviewed by the usual crowd, but still waiting for
> a "maintainer" to respond..
Should we include that in linux-next?
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-next@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: new xfs git tree
Date: Mon, 26 Jan 2009 22:41:30 -0800 [thread overview]
Message-ID: <20090126224130.53949fda.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090119011601.GA14708@infradead.org>
On Sun, 18 Jan 2009 20:16:01 -0500 Christoph Hellwig <hch@infradead.org> wrote:
> git://git.kernel.org/pub/scm/fs/xfs/xfs.git has all the fixes the
> have been peer-reviewed by the usual crowd, but still waiting for
> a "maintainer" to respond..
Should we include that in linux-next?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-27 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 1:16 new xfs git tree Christoph Hellwig
2009-01-27 6:41 ` Andrew Morton [this message]
2009-01-27 6:41 ` Andrew Morton
2009-01-29 21:14 ` Felix Blyakher
2009-01-29 21:14 ` Felix Blyakher
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=20090126224130.53949fda.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-next@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.