From: Carlos Maiolino <cmaiolino@redhat.com>
To: xfs@oss.sgi.com
Subject: Re: userspace trees
Date: Thu, 13 Sep 2012 11:22:29 -0300 [thread overview]
Message-ID: <20120913142229.GA4382@andromeda.usersys.redhat.com> (raw)
In-Reply-To: <20120913075026.GA27256@infradead.org>
On Thu, Sep 13, 2012 at 03:50:26AM -0400, Christoph Hellwig wrote:
> It seems with the kernel.org account purge last year and me being way to
> busy it seems like the -dev trees of the XFS userspace get very little
> attention. What do people think about retiring them and using the oss
> trees exclusively again for now? Right now the trees are getting a bit
> out of sync which isn't a good thing.
>
Maintaining oss only looks easier to me and less error prone (in regards on keep
trees synchronized) than still keep the kernel.org xfs tree.
To be honest I've never used the kernel.org xfs trees, so, at least for me this
makes sense.
--
--Carlos
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-09-13 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 7:50 userspace trees Christoph Hellwig
2012-09-13 14:22 ` Carlos Maiolino [this message]
2012-09-13 17:13 ` Eric Sandeen
2012-09-13 17:53 ` Ben Myers
2012-09-13 17:54 ` Eric Sandeen
2012-09-13 20:10 ` Ben Myers
2012-09-13 20:13 ` Eric Sandeen
2012-09-25 9:29 ` Christoph Hellwig
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=20120913142229.GA4382@andromeda.usersys.redhat.com \
--to=cmaiolino@redhat.com \
--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