mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Brian Gerst <bgerst@didntduck.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	Linus Torvalds <torvalds@transmeta.com>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Update fs Makefiles
Date: Tue, 20 May 2003 17:33:41 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0305201726200.12110-100000@serv> (raw)
In-Reply-To: <Pine.LNX.4.44.0305200940130.24017-100000@chaos.physics.uiowa.edu>

Hi,

On Tue, 20 May 2003, Kai Germaschewski wrote:

> > >>-adfs-objs := dir.o dir_f.o dir_fplus.o file.o inode.o map.o super.o
> > >>+adfs-y := dir.o dir_f.o dir_fplus.o file.o inode.o map.o super.o
> > > 
> > > 
> > 
> > Why have two methods of doing the same thing?  foo-y is clearly the 
> > preferred method because it is easy to work with conditionals.
> 
> I tend to agree, though I don't feel strongly about it. Having two 
> different methods of expressing the same thing will always be confusing. 

Has the new syntax any advantage, e.g. does it make sense to have adfs-m? 
Otherwise the -obj syntax looks IMO more readable and it directly says 
that this is a composite object.

bye, Roman


  parent reply	other threads:[~2003-05-20 15:23 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
2003-05-20 15:33       ` Roman Zippel [this message]
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=Pine.LNX.4.44.0305201726200.12110-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=bgerst@didntduck.org \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@transmeta.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®