public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: Why not move xfs infra-structure to "public" services
Date: Tue, 30 Sep 2014 09:46:36 -0500	[thread overview]
Message-ID: <542AC24C.8030907@sandeen.net> (raw)
In-Reply-To: <20140930141857.GA2053@localhost.localdomain>

On 9/30/14 9:18 AM, Carlos Maiolino wrote:
> Hi guys,
> 
> I'm sorry for this kind of "fancy" question from my side, but I'm wondering why
> xfs project infra-structure (mailing list, git trees), does not use the "usual
> public" services. I mean, does anyone thought about moving xfs mailing list to
> vger.kernel.org, and the git trees to git.kernel.org?

Please see the prior thread on 8/6/14:
[DISCUSS] Moving from oss.sgi.com to kernel.org

:)

> Sorry about been asking it mainly because I'm too lazy to keep deleting spams
> from my inbox, and also, because having 'everything I need' in a single place
> (kernel.org) would make my life easier (and probably many other lives :).
> 
> Anyway, it's just a question/suggestion, please don't get me wrong here.
> IIRC there were some discussion regarding this some time ago, but, I'm not
> sure where the discussion stopped and/or if any decision were taken.

I think it's still the plan, but takes some time & effort & coordination.

-Eric

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

  reply	other threads:[~2014-09-30 14:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 14:18 Why not move xfs infra-structure to "public" services Carlos Maiolino
2014-09-30 14:46 ` Eric Sandeen [this message]
2014-09-30 15:02   ` Carlos Maiolino
2014-09-30 17:55 ` Arkadiusz Miśkiewicz
2014-09-30 20:00 ` Dave Chinner
2014-09-30 20:12   ` Carlos Maiolino
2014-09-30 20:42     ` Dave Chinner

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=542AC24C.8030907@sandeen.net \
    --to=sandeen@sandeen.net \
    --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