From: Christoph Hellwig <hch@infradead.org>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Mike Frysinger <vapier@gentoo.org>,
Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>,
Christoph Hellwig <hch@infradead.org>,
Nathan Scott <nathans@debian.org>,
Greg Banks <gnb@melbourne.sgi.com>
Subject: Re: [patch] fix parallel build failures in xfsprogs-3.0.0
Date: Tue, 3 Mar 2009 10:55:23 -0500 [thread overview]
Message-ID: <20090303155523.GC26376@infradead.org> (raw)
In-Reply-To: <200903011823.09613.agruen@suse.de>
On Sun, Mar 01, 2009 at 06:23:09PM +0100, Andreas Gruenbacher wrote:
> Yes, makes sense. I've copied Christoph's tree over and set up permissions;
> you should have access now.
>
> Greg doesn't have a kernel.org account yet, so I can't give him access at the
> moment.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/agruen/nfs4acl.git
> ssh://master.kernel.org/pub/scm/linux/kernel/git/agruen/nfs4acl.git
>
> Would you like write access to the attr.git and acl.git trees as well?
Greg or me? Don't think I want to do too much on it. I'll just bounce
you whatever build system updates seem like fitting for acl/attr too.
Still a few I need to send you.
But Nathan Scott might want it as he wants to keep the debian packaging
in the upstream git, and I suspect acl/attr aren't different from the
xfs tools in that respect.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-03-03 15:55 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 5:10 [patch] fix parallel build failures in xfsprogs-3.0.0 Mike Frysinger
2009-02-24 5:20 ` Eric Sandeen
2009-02-24 5:22 ` Eric Sandeen
2009-02-24 7:21 ` Mike Frysinger
2009-02-24 13:15 ` Christoph Hellwig
2009-02-24 14:53 ` Mike Frysinger
2009-02-24 15:14 ` Felix Blyakher
2009-02-24 15:37 ` Mike Frysinger
2009-02-24 18:46 ` Christoph Hellwig
2009-02-24 22:22 ` Andreas Gruenbacher
2009-02-24 23:45 ` Mike Frysinger
2009-02-26 0:26 ` Andreas Gruenbacher
2009-02-26 1:03 ` Mike Frysinger
2009-02-26 12:23 ` Andreas Gruenbacher
2009-02-26 15:17 ` Mike Frysinger
2009-02-26 17:17 ` Andreas Gruenbacher
2009-02-26 18:08 ` Mike Frysinger
2009-02-27 7:22 ` Greg Banks
2009-02-27 9:55 ` Andreas Gruenbacher
2009-03-01 1:31 ` Greg Banks
2009-03-01 7:58 ` Mike Frysinger
2009-03-03 15:53 ` Christoph Hellwig
2009-02-27 17:35 ` Andreas Gruenbacher
2009-03-04 17:27 ` Christoph Hellwig
2009-03-08 13:09 ` Andreas Gruenbacher
2009-03-10 16:41 ` Andreas Gruenbacher
2009-03-16 7:05 ` Christoph Hellwig
2009-03-16 7:31 ` Mike Frysinger
2009-03-16 9:53 ` Andreas Gruenbacher
2009-03-16 21:02 ` Christoph Hellwig
2009-03-24 13:12 ` Christoph Hellwig
2009-03-24 18:18 ` Andreas Gruenbacher
2009-03-25 19:03 ` Christoph Hellwig
2009-03-16 6:51 ` Christoph Hellwig
2009-03-27 16:02 ` Christoph Hellwig
2009-03-27 16:30 ` Mike Frysinger
2009-03-27 18:31 ` Christoph Hellwig
2009-02-26 23:03 ` Christoph Hellwig
2009-02-28 0:07 ` Andreas Gruenbacher
2009-02-28 22:27 ` Eric Sandeen
2009-03-01 1:41 ` Greg Banks
2009-03-01 17:23 ` Andreas Gruenbacher
2009-03-03 15:55 ` Christoph Hellwig [this message]
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=20090303155523.GC26376@infradead.org \
--to=hch@infradead.org \
--cc=agruen@suse.de \
--cc=gnb@melbourne.sgi.com \
--cc=nathans@debian.org \
--cc=sandeen@sandeen.net \
--cc=vapier@gentoo.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