All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 16 Apr 2009 09:54:24 -0500	[thread overview]
Message-ID: <49E746A0.5020008@sandeen.net> (raw)
In-Reply-To: <49E6ED88.5020008@tlinx.org>

Linda A. Walsh wrote:
> Eric Sandeen wrote:
>> Linda A. Walsh wrote:
>>> 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'?
>> 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.
> ---
>     Would hope not -- but have seen companies pull real bonehead maneuvers.
> 
> I can understand that for kernel work, but what about the xfs utils? 

Again, just look at the git logs.

-Eric

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

  reply	other threads:[~2009-04-16 14:54 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
2009-04-16  8:34   ` Linda A. Walsh
2009-04-16 14:54     ` Eric Sandeen [this message]
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=49E746A0.5020008@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.