From: Carlos Maiolino <cmaiolino@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: Why not move xfs infra-structure to "public" services
Date: Tue, 30 Sep 2014 12:02:12 -0300 [thread overview]
Message-ID: <20140930150211.GB2053@localhost.localdomain> (raw)
In-Reply-To: <542AC24C.8030907@sandeen.net>
> Please see the prior thread on 8/6/14:
> [DISCUSS] Moving from oss.sgi.com to kernel.org
>
I will :)
> :)
>
> > 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.
>
Thanks for the answer. And, if people need help to move it, let me know, I'm
willing to spend time helping the move.
cheers
> -Eric
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
--
Carlos
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-09-30 15:02 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
2014-09-30 15:02 ` Carlos Maiolino [this message]
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=20140930150211.GB2053@localhost.localdomain \
--to=cmaiolino@redhat.com \
--cc=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