public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: akpm@osdl.org, sfr@canb.auug.org.au, xfs@oss.sgi.com
Subject: Re: xfsdev tree in linux-next?
Date: Fri, 02 Jul 2010 15:56:06 -0500	[thread overview]
Message-ID: <1278104166.1876.134.camel@doink> (raw)
In-Reply-To: <20100702103951.GA18369@infradead.org>

On Fri, 2010-07-02 at 06:39 -0400, Christoph Hellwig wrote:
> Hi Steve,
> 
> we've got a massive backlog of over a month worth of patches that have
> been reviewed on the XFS list and QAed by Dave and me but not picked up
> yet into the official tree.
> 
> Can you temporarily add
> 
> 	git://git.kernel.org/pub/scm/linux/kernel/git/dgc/xfsdev.git for-2.6.36
> 
> to the linux-next lineup so what we can get more testing exposure?
> 

FYI I will have git://oss.sgi.com/xfs/xfs.git master up-to-date
today.  I'm waiting for some testing to finish before pushing
out all the recent updates.  I'm sorry about the delay.

					-Alex

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2010-07-02 20:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02 10:39 xfsdev tree in linux-next? Christoph Hellwig
2010-07-02 20:56 ` Alex Elder [this message]

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=1278104166.1876.134.camel@doink \
    --to=aelder@sgi.com \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --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