mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: xfs: Makefile-linux-2.6 => Makefile?
Date: Mon, 9 Jan 2006 22:18:11 +0100	[thread overview]
Message-ID: <20060109211811.GB14477@mars.ravnborg.org> (raw)
In-Reply-To: <20060109210540.GA9972@infradead.org>

On Mon, Jan 09, 2006 at 09:05:40PM +0000, Christoph Hellwig wrote:
> > +#
> > +# The xfs people like to share Makefile with 2.6 and 2.4.
> > +# Utilise file named Kbuild file which has precedence over Makefile.
> > +#
> > +
> > +include $(srctree)/$(obj)/Makefile-linux-2.6
> 
> What about just putting the content of the current Makefile-linux-2.6
> into the Kbuild file directly?
People do not expect this - since the Kbuild filename is not used expect in
the top-level directory.
So as a principle of minimum suprise I left the old Makefile as-is,
and introduced the new Kbuild file.
If xfs people likes it different then they can change it anytime.

If I one day start my little "kbuild file parser to a single makefile" project
it may be the day where we do the transition.

	Sam

  reply	other threads:[~2006-01-09 21:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 16:42 Sam Ravnborg
2006-01-09 16:46 ` Christoph Hellwig
2006-01-09 17:19   ` Sam Ravnborg
2006-01-09 21:01   ` Sam Ravnborg
2006-01-09 21:05     ` Christoph Hellwig
2006-01-09 21:18       ` Sam Ravnborg [this message]
2006-01-09 21:03   ` Eric Sandeen
2006-01-09 21:20     ` Sam Ravnborg
2006-01-09 21:23       ` Eric Sandeen
2006-01-09 21:45         ` Sam Ravnborg
2006-01-10  7:45     ` Andrew Morton
2006-01-10 15:14       ` Eric Sandeen
2006-01-10 16:34       ` Eric Sandeen
2006-01-10 20:02         ` Sam Ravnborg
2006-01-16 23:19         ` Sam Ravnborg
2006-01-17  3:40           ` Eric Sandeen
2006-01-10 20:00       ` Sam Ravnborg

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=20060109211811.GB14477@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-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

all inboxes | Powered by JetHome®