public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: aurel32@debian.org, nathans@debian.org, anibal@debian.org
Cc: xfs@oss.sgi.com
Subject: The xfsprogs debian package
Date: Mon, 19 Sep 2011 13:10:47 -0400	[thread overview]
Message-ID: <20110919171047.GA3092@infradead.org> (raw)
In-Reply-To: <20110919170936.GA27014@infradead.org>

[and now with the correct Cc list]

On Mon, Sep 19, 2011 at 01:09:36PM -0400, Christoph Hellwig wrote:
> Hi Aurelien, Nathan & Anibal,
> 
> is there any chance we can get to a defintive agreement on how to
> maintain the xfsprogs package?  So far the idea of releasing the
> upstream releases as Debian packages at the same time has worked
> great for both Debian, and us xfs developers (which to a large
> extents are heavy Debian users), but "inner" Debian circles heave
> always complained about it.
> 
> Can we please get an explanation of why it is so in proper written
> englush, instead of doing by forced nmus?
> 
> Also Nathan & Anibal - if there is no consesus for keeping the old
> scheme what about dropping it?  We can still keep the main Debian
> packaging in the tree, and find a way to generate a normally NULL
> Debian diff for it.  I'm not quite sure how to do it, but there
> must be some way.
---end quoted text---

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

       reply	other threads:[~2011-09-19 17:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110919170936.GA27014@infradead.org>
2011-09-19 17:10 ` Christoph Hellwig [this message]
2011-09-20 10:58   ` The xfsprogs debian package Aurelien Jarno
2011-09-20 22:48     ` Nathan Scott
2011-09-21  1:21       ` Aníbal Monsalve Salazar

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=20110919171047.GA3092@infradead.org \
    --to=hch@infradead.org \
    --cc=anibal@debian.org \
    --cc=aurel32@debian.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