From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: Re: Why not move xfs infra-structure to "public" services
Date: Wed, 1 Oct 2014 06:00:46 +1000 [thread overview]
Message-ID: <20140930200046.GQ4758@dastard> (raw)
In-Reply-To: <20140930141857.GA2053@localhost.localdomain>
On Tue, Sep 30, 2014 at 11:18:57AM -0300, 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?
I'm already using git.kernel.org for my master XFS trees. The ones
on oss.sgi.com are simply now downstream mirrors. There's still a
few things I need to organise (e.g. where release tarballs are put)
before we make the kernel.org trees the official source of XFS
source code.
We already have a linux-xfs@vger.kernel.org mailing list - we just
don't use it. Again, more organisation stuff to do to switch over
(i.e. forwarding from xfs@oss.sgi.com to the vger list) and then
updating documentation everywhere and getting people to start using
it.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-09-30 20:00 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
2014-09-30 17:55 ` Arkadiusz Miśkiewicz
2014-09-30 20:00 ` Dave Chinner [this message]
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=20140930200046.GQ4758@dastard \
--to=david@fromorbit.com \
--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 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.