public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: nathans@aconex.com
To: "Aníbal Monsalve Salazar" <anibal@debian.org>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: xfsprogs Debian mantainaince
Date: Fri, 1 Oct 2010 11:35:58 +1000 (EST)	[thread overview]
Message-ID: <1484205641.1495781285896958375.JavaMail.root@mail-au.aconex.com> (raw)
In-Reply-To: <727678297.1495351285896368345.JavaMail.root@mail-au.aconex.com>


----- "Aníbal Monsalve Salazar" <anibal@debian.org> wrote:
> 
> Hi Christoph and Nathan, :)

Hey Anibal!

> Any news about access to kernel.org to merge changes before
> uploading?
> 
> Having the xfsprogs Debian package as native is okay for me if that
> is what you guys want.

Yep.

> Some Debian maintainers think it isn't a good idea, however.

If you assert that grass is green and the sky is blue, you will find
some Debian maintainers disagree with you.  ;)  And fair enough too,
everyones entitles to an opinion.

cheers.

--
Nathan

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

       reply	other threads:[~2010-10-01  1:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <727678297.1495351285896368345.JavaMail.root@mail-au.aconex.com>
2010-10-01  1:35 ` nathans [this message]
     [not found] <97008679.1517661285974121218.JavaMail.root@mail-au.aconex.com>
2010-10-01 23:02 ` xfsprogs Debian mantainaince nathans
2010-10-02  1:34   ` Aníbal Monsalve Salazar
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=1484205641.1495781285896958375.JavaMail.root@mail-au.aconex.com \
    --to=nathans@aconex.com \
    --cc=anibal@debian.org \
    --cc=hch@infradead.org \
    --cc=nathans@debian.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