mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@quark.didntduck.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: mikpe@csd.uu.se, Brian Gerst <bgerst@didntduck.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Update fs Makefiles
Date: Tue, 20 May 2003 18:54:28 -0400	[thread overview]
Message-ID: <3ECAB224.9070002@quark.didntduck.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0305201139020.24017-100000@chaos.physics.uiowa.edu>

Kai Germaschewski wrote:
> On Tue, 20 May 2003 mikpe@csd.uu.se wrote:
> 
> 
>>Kai Germaschewski writes:
>> > o Possibly add "-y" support to 2.4 (it's a pretty trivial change)
>>
>>That's the worst thing you could do for those of us maintaining
>>2.4/2.5 compatibility in drivers etc.
>>Having to check "oh I'm in 2.4, let's see if I'm in 2.4.23 or
>>$VENDOR 2.4.blah because then these random 2.5-like changes occurred"
>>sucks like h*ll.
> 
> 
> It'd be an additional feature, i.e. if it causes trouble for the code you 
> maintain, don't use it.
> 
> People who want a Makefile which works in all 2.4 + vendor then would 
> choose to stay with -objs, whereas people who prefer do have 2.4.latest 
> and 2.5 in sync could use -y, like, I'd guess, USB.
> 
> --Kai

Easiest way to maintain 2.4 compatability is to add:

foo-objs := $(foo-y)

--
				Brian Gerst



  reply	other threads:[~2003-05-20 22:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-19  0:51 Brian Gerst
2003-05-19 17:02 ` Sam Ravnborg
2003-05-19 21:55   ` Brian Gerst
2003-05-20 14:47     ` Kai Germaschewski
2003-05-20 15:14       ` mikpe
2003-05-20 16:41         ` Kai Germaschewski
2003-05-20 22:54           ` Brian Gerst [this message]
2003-05-20 15:33       ` Roman Zippel
2003-05-20 16:38         ` Kai Germaschewski
2003-05-20 18:34       ` 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=3ECAB224.9070002@quark.didntduck.org \
    --to=bgerst@quark.didntduck.org \
    --cc=bgerst@didntduck.org \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=sam@ravnborg.org \
    /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®