From: Niv Sardi <xaiki@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: New XFS git tree on oss.sgi.com
Date: Thu, 04 Dec 2008 10:58:48 +1100 [thread overview]
Message-ID: <871vwo95fr.fsf@cxhome.ath.cx> (raw)
In-Reply-To: <20081203130414.GB9681@infradead.org> (Christoph Hellwig's message of "Wed, 3 Dec 2008 08:04:14 -0500")
Christoph Hellwig <hch@infradead.org> writes:
> On Wed, Dec 03, 2008 at 02:48:57PM +1100, Niv Sardi wrote:
>
>> > Also
>> > http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs.git;a=commitdiff;h=ca830fdf6231d0683f4ea4e9223e234c3a509063doesn't seem to be needed. None of those symbols seems to be used by
>> > either dmapi or xfsidbg, the only two modules using xfs symbols in the
>> > tree.
>>
>> That's exactly why it's there, the revertion is actually moving from
>> what was in ptools to something sane.
>
> ?? The commit above adds tons of unused exports. But hey, I'll just
> submit a patch to sort it out when I get some time..
Yes, I already did that …that's the previous commit… but Lachland wanted
the tree not too move too much at first.
The patch you want is the exact revert of the commit you pointed out,
it'll be checked in soon.
Cheers,
--
Niv Sardi
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-12-04 0:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 7:22 New XFS git tree on oss.sgi.com Lachlan McIlroy
2008-11-25 8:16 ` Christoph Hellwig
2008-11-25 14:27 ` Russell Cattelan
2008-11-25 21:42 ` Mark Goodwin
2008-11-26 3:30 ` Christoph Hellwig
2008-11-26 3:36 ` Russell Cattelan
2008-11-26 1:03 ` Lachlan McIlroy
2008-11-26 1:17 ` Timothy Shimmin
2008-11-26 3:26 ` Russell Cattelan
2008-12-03 3:37 ` Niv Sardi
2008-12-09 9:17 ` Christoph Hellwig
2008-12-09 16:20 ` Russell Cattelan
2008-12-09 16:57 ` Christoph Hellwig
2008-12-09 17:12 ` Russell Cattelan
2008-12-09 22:20 ` Niv Sardi
2008-12-10 0:07 ` Russell Cattelan
2008-12-10 0:46 ` Mark Goodwin
2008-12-10 1:14 ` Niv Sardi
2008-12-10 6:51 ` Christoph Hellwig
2008-11-26 3:30 ` Christoph Hellwig
2008-11-26 1:00 ` Lachlan McIlroy
2008-11-26 2:00 ` Dave Chinner
2008-11-26 3:29 ` Timothy Shimmin
2008-11-26 4:08 ` Dave Chinner
2008-11-26 5:41 ` Timothy Shimmin
2008-12-04 13:26 ` Christoph Hellwig
2008-12-05 3:29 ` Niv Sardi
2008-12-03 3:45 ` Niv Sardi
2008-11-26 3:28 ` Christoph Hellwig
2008-11-25 14:05 ` Christoph Hellwig
2008-11-26 1:11 ` Lachlan McIlroy
2008-11-26 3:27 ` Christoph Hellwig
2008-12-03 3:48 ` Niv Sardi
2008-12-03 13:04 ` Christoph Hellwig
2008-12-03 23:58 ` Niv Sardi [this message]
2008-12-04 12:34 ` Christoph Hellwig
2008-11-26 3:40 ` Eric Sandeen
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=871vwo95fr.fsf@cxhome.ath.cx \
--to=xaiki@sgi.com \
--cc=hch@infradead.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