From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Lachlan McIlroy <lachlan@sgi.com>, xfs@oss.sgi.com
Subject: Re: [GIT PULL] XFS update for 2.6.25
Date: Fri, 08 Feb 2008 22:58:53 -0600 [thread overview]
Message-ID: <47AD330D.3010603@sandeen.net> (raw)
In-Reply-To: <20080209045645.GB1428@infradead.org>
Christoph Hellwig wrote:
> On Fri, Feb 08, 2008 at 10:13:03PM -0600, Eric Sandeen wrote:
>> Lachlan McIlroy wrote:
>>> Please pull from the for-linus branch:
>>> git pull git://oss.sgi.com:8090/xfs/xfs-2.6.git for-linus
>>>
>>> This will update the following files:
>>>
>>> fs/xfs/Makefile-linux-2.6 | 1 -
>> Is there a reason the other various makefile updates still haven't been
>> pushed? They're a lot tidier now, and they facilitate out-of-tree
>> building...
>
> Well, the makefiles are pretty different for CVS vs mainline to modular
> quota and dmapi. I'm thinking about doing a proof of concept modular
> quota patch for mainline and if it doesn't get too ugly that would
> mean the makefiles are a lot more in sync.
Even if they differ, they can still get the same basic treatment. I'll
make a patch if desired. The current kernel.org makefiles are a mess,
IMHO :)
-Eric
next prev parent reply other threads:[~2008-02-09 4:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 2:27 [GIT PULL] XFS update for 2.6.25 Lachlan McIlroy
2008-02-09 4:13 ` Eric Sandeen
2008-02-09 4:56 ` Christoph Hellwig
2008-02-09 4:58 ` Eric Sandeen [this message]
2008-02-09 5:03 ` Christoph Hellwig
2008-02-09 5:09 ` [PATCH 1/2] - unwrap makefiles (mainline only) Eric Sandeen
2008-02-09 5:13 ` [PATCH 2/2] fix up out of tree builds " Eric Sandeen
2008-02-11 4:57 ` [GIT PULL] XFS update for 2.6.25 Lachlan McIlroy
2008-02-11 4:57 ` 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=47AD330D.3010603@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@infradead.org \
--cc=lachlan@sgi.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.