From: Eric Sandeen <sandeen@sandeen.net>
To: "Linda A. Walsh" <xfs@tlinx.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: future of xfs, oss.sgi.com after sgi purchased?
Date: Wed, 15 Apr 2009 23:41:27 -0500 [thread overview]
Message-ID: <49E6B6F7.6030500@sandeen.net> (raw)
In-Reply-To: <49E65044.8080802@tlinx.org>
Linda A. Walsh wrote:
> Not one to beat about the bush, but curious from a practical sense,
>
> If sgi is being bought by another company, is there any idea about the plans
> for the xfs file system or the source code on 'oss.sgi.com'?
>
> I'm _guessing_ that there is some interest in users and developers to keep xfs
> alive after the 'sgi' moniker is purchased, but that begs the question about the
> new company wanting to support the old 'sgi.com' websites including
> oss.sgi.com.
>
> Is there a danger of oss.sgi.com suddenly being yanked offline with little to no
> warning, such that community members should start keeping up-to-date, or is it
> already mirrored? I'm assuming that the current source code repository only
> exists on oss.sgi.com? Should it be mirrored on some other external open-source
> site? sourceforge? google? mozilla?
While I doubt that oss.sgi.com would abruptly vanish, there are
nonetheless already git repos on kernel.org, which are sometimes even
ahead of what's on oss.sgi.com ... xfs.org has a lot of content as well.
Mailing list archives exist at various other sites.
There are also ftp mirrors around, though I think that's less important.
> Is completely worthless to discuss new, desired features in some of the utils?
> Will it be possible to support the xfs codebase if its development no longer
> becomes necessary to sgi (or its parent company)?
If you look at commit logs or carefully read the mailing list over the
last 6 months or so, I think you'll find that xfs maintenance and
development is not wholly dependent on contributions from sgi employees.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=fs/xfs;hb=HEAD
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-04-16 4:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 21:23 future of xfs, oss.sgi.com after sgi purchased? Linda A. Walsh
2009-04-16 4:41 ` Eric Sandeen [this message]
2009-04-16 8:34 ` Linda A. Walsh
2009-04-16 14:54 ` Eric Sandeen
2009-04-16 18:36 ` getting changes (fixes or enhancements) to xfs-tools Linda A. Walsh
2009-04-16 20:50 ` Eric Sandeen
2009-04-16 21:15 ` Felix Blyakher
2009-04-16 6:05 ` future of xfs, oss.sgi.com after sgi purchased? Felix Blyakher
2009-04-16 15:54 ` Russell Cattelan
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=49E6B6F7.6030500@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
--cc=xfs@tlinx.org \
/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