From: Eric Sandeen <sandeen@sandeen.net>
To: Ben Myers <bpm@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: userspace trees
Date: Thu, 13 Sep 2012 12:54:22 -0500 [thread overview]
Message-ID: <50521DCE.7020203@sandeen.net> (raw)
In-Reply-To: <20120913175316.GR3274@sgi.com>
On 9/13/12 12:53 PM, Ben Myers wrote:
> Hi Eric,
>
> On Thu, Sep 13, 2012 at 12:13:15PM -0500, Eric Sandeen wrote:
>> On 9/13/12 2:50 AM, 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.
>>
>> ISTR it was done in response to a .... fear of SGI being less responsive after
>> a different type of account purge. ;)
>>
>> If SGI wants to be responsible for merging all userspace patches as they
>> come in on the list, I'm fine with going back to one tree on oss.
>
> I discussed this with management. SGI is willing to take on the responsibility
> of merging all userspace patches.
>
> I think retiring the -dev trees will resolve the out-of-sync issues we've been
> having, and be less confusing for all involved.
Sounds like a plan. Will you make sure everything gets re-synced from kernel.org
so nothing is lost?
hch, you want to remove or somehow deprecate the kernel.org trees?
Thanks,
-Eric
> Regards,
> Ben
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-09-13 17:53 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
2012-09-13 17:13 ` Eric Sandeen
2012-09-13 17:53 ` Ben Myers
2012-09-13 17:54 ` Eric Sandeen [this message]
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=50521DCE.7020203@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bpm@sgi.com \
--cc=hch@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox