public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: nathans@debian.org, anibal@debian.org
Cc: xfs@oss.sgi.com
Subject: xfsprogs Debian mantainaince
Date: Sat, 14 Aug 2010 07:15:13 -0400	[thread overview]
Message-ID: <20100814111513.GA8214@infradead.org> (raw)

Hi Nathan, hi Anibal,

if seen the constant flipping between native and non-native uploads
for the xfsprogs Debian packages between the two of you and it's
slightly annoying.  I know Nathan likes maintaining the Debian packages
in git, which also makes life for us XFS developers trying to build
debian packages a lot easier.

What about a compromise?  We'll add a debian-<dist> branches to the
xfsprogs-dev repository where we can track the exact packages uploaded
to Debian, including the -2/-3 etc packages revisions that only get
uploaded to Debian, while all important packaging changes happen in
the master branch, so that it can also be built from git into a Debian
package.  The advantage is that all package maintaince happens in git,
git master can be packaged easily, and in addition we track all Debian
uploads in git as well.  The only big prerequisite is that we get
a kernel.org account for Anibal so that he can also commit to it
directly.

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.

All this also applies to xfsdump and the dmapi package, too.

And one last request, any chance to get xfsprogs for -testing rebuilt
against libblkid now that util-linux-2.17 has finally made it into
testing?  Beeing able to use blkid for alignment detection will be
very important so that XFS on Debian can deal with 4k sector disks
and hardware RAID arrays out of the box.

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

             reply	other threads:[~2010-08-14 11:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-14 11:15 Christoph Hellwig [this message]
2010-08-16  1:25 ` xfsprogs Debian mantainaince 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
     [not found] <727678297.1495351285896368345.JavaMail.root@mail-au.aconex.com>
2010-10-01  1:35 ` nathans
     [not found] <97008679.1517661285974121218.JavaMail.root@mail-au.aconex.com>
2010-10-01 23:02 ` nathans
2010-10-02  1:34   ` 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=20100814111513.GA8214@infradead.org \
    --to=hch@infradead.org \
    --cc=anibal@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