public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Goodwin <markgw@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, xfs@oss.sgi.com
Subject: Re: Announce: XFS staging tree
Date: Sat, 22 Nov 2008 10:07:34 +1100	[thread overview]
Message-ID: <49273F36.7040302@sgi.com> (raw)
In-Reply-To: <20081121212030.GA17816@infradead.org>



Christoph Hellwig wrote:
> I've created a new tree of all patches that have been reviewed, and
> properly QAed but haven't been merged into the SGI tree for reasons
> unknown to us patch submitters.

Lachlan has about 30 patches almost ready to push back out (mostly yours
Christoph). Sorry for the delays and the frustration this is causing. Just
waiting for some back-end constipation with ptools to resolve, which will
happen early next week.

> I'll add all patches that have gotten review on linux-xfs to it after
> they pass xfsqa for me.   Patches will be dropped as soon as they get
> into the xfs git tree.

On-going, this might be a better way to manage the patch queue, at least
possibly better in terms of front-line QA. Maybe an almost-open-access
git repository for incomming patches could work too. What do others think?

Cheers
-- Mark

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

      reply	other threads:[~2008-11-21 23:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 21:20 Announce: XFS staging tree Christoph Hellwig
2008-11-21 23:07 ` Mark Goodwin [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=49273F36.7040302@sgi.com \
    --to=markgw@sgi.com \
    --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