public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aníbal Monsalve Salazar" <anibal@debian.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: nathans@debian.org, xfs@oss.sgi.com, Nathan Scott <nathans@aconex.com>
Subject: Re: xfsprogs Debian mantainaince
Date: Fri, 1 Oct 2010 11:02:26 +1000	[thread overview]
Message-ID: <20101001010226.GB3066@master.debian.org> (raw)
In-Reply-To: <20100829041924.GB2648@mapuche.apana.org.au>

On Sun, Aug 29, 2010 at 02:19:24PM +1000, Anibal Monsalve Salazar wrote:
>On Mon, Aug 16, 2010 at 11:25:59AM +1000, Nathan Scott wrote:
>>----- "Christoph Hellwig" <hch@infradead.org> wrote:
>>
>>>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.
>
>Sorry about the unintended nuisance. When I had access to the SGI ptools
>repo it was very easy to keep my uploads to Debian with an updated
>debian directory. 
>
>>>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,
>>
>>IMO, the -2 and -3 revisions are unnecessary and there's really no need
>>for a separate branch ... if Anibal had a kernel.org account and merged
>>changes in before uploading, there'd be no issue, I think - Anibal?  It
>>would make life simpler, for sure.
>
>I agree.

Hi Christoph and Nathan, :)

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. Some Debian maintainers think it isn't a good idea,
however.

Cheers.

>On the same subject, I talked to Andreas during LinuxCon2010 in Boston
>about getting access to the acl and attr git repos to update the debian
>directory before uploading packages to Debian. He was very positive
>about that.
>
>>>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.
>>
>>Sure, I'll take a look at that for next upload.
>>
>>cheers.
>>
>>-- 
>>Nathan

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

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-14 11:15 xfsprogs Debian mantainaince 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 [this message]
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=20101001010226.GB3066@master.debian.org \
    --to=anibal@debian.org \
    --cc=hch@infradead.org \
    --cc=nathans@aconex.com \
    --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