From: nathans@debian.org
To: Christoph Hellwig <hch@infradead.org>
Cc: nathans@debian.org, anibal@debian.org, xfs@oss.sgi.com
Subject: Re: xfsprogs Debian mantainaince
Date: Sat, 2 Oct 2010 09:02:51 +1000 (EST) [thread overview]
Message-ID: <1371146962.1517681285974171988.JavaMail.root@mail-au.aconex.com> (raw)
In-Reply-To: <97008679.1517661285974121218.JavaMail.root@mail-au.aconex.com>
----- "Christoph Hellwig" <hch@infradead.org> wrote:
> On Sat, Aug 14, 2010 at 07:15:13AM -0400, Christoph Hellwig wrote:
> > Also can we add xfs@oss.sgi.com to the Cc list for debian xfs
> > bugreports? I think most issues are upstream ones anyway, and
> > automatically sending them to the XFS list will get them a bigger
> > audience.
>
> Guys, any idea how to get this done?
Not sure ... I'm guessing we need to make an "official" xfs
debian maintenance team. Probably some process exists for
that, somewhere, which I haven't been able to find so far -
Anibal do you know? (http://wiki.debian.org/Teams looks like
a place to start?) and then add xfs@oss as a contact address
on that list.
cheers.
--
Nathan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next parent reply other threads:[~2010-10-01 23:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <97008679.1517661285974121218.JavaMail.root@mail-au.aconex.com>
2010-10-01 23:02 ` nathans [this message]
2010-10-02 1:34 ` xfsprogs Debian mantainaince Aníbal Monsalve Salazar
[not found] <727678297.1495351285896368345.JavaMail.root@mail-au.aconex.com>
2010-10-01 1:35 ` nathans
2010-08-14 11:15 Christoph Hellwig
2010-08-16 1:25 ` Nathan Scott
2010-08-29 4:19 ` Aníbal Monsalve Salazar
2010-10-01 1:02 ` Aníbal Monsalve Salazar
2010-10-01 8:35 ` Christoph Hellwig
2010-10-01 8:36 ` Christoph Hellwig
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=1371146962.1517681285974171988.JavaMail.root@mail-au.aconex.com \
--to=nathans@debian.org \
--cc=anibal@debian.org \
--cc=hch@infradead.org \
--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