From: Mike Frysinger <vapier@gentoo.org>
To: Felix Blyakher <felixb@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [patch] fix parallel build failures in xfsprogs-3.0.0
Date: Tue, 24 Feb 2009 10:37:49 -0500 [thread overview]
Message-ID: <200902241037.50534.vapier@gentoo.org> (raw)
In-Reply-To: <3C7B0B6E-1316-41CC-8846-356FDC780287@sgi.com>
[-- Attachment #1.1: Type: text/plain, Size: 1038 bytes --]
On Tuesday 24 February 2009 10:14:13 Felix Blyakher wrote:
> On Feb 24, 2009, at 8:53 AM, Mike Frysinger wrote:
> > the xfs.org wiki talks about git trees on sgi.com,
>
> Yes, they're still there.
>
> > but some of them are old
> > and/or moved (like the xfs-cmds one) ...
>
> xfs-cmds was split into separate repos for xfsprogs, xfsdump,
> and dmapi. And that info is on xfs.org.
but acl/attr have not. distros care about those packages as well.
> Here is the excerpt from the following page:
yes, i was reading the page. i was also pointing out the broken link to the
xfs-cmds repo (which is after everything you quoted) and that that repo seems
to be dead now. which means there is no up-to-date place for acl/attr on that
page.
> At times though the repos on kernel.org could be ahead of sgi ones.
well if people are going to try to help in development, the kernel.org trees
would be good to mention on that page as well with a note as to which tree is
preferred (sgi.com or kernel.org).
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-24 15:38 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 [this message]
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
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=200902241037.50534.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=felixb@sgi.com \
--cc=hch@infradead.org \
--cc=sandeen@sandeen.net \
--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