LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org> To: Linus Torvalds <torvalds@linux-foundation.org> Cc: linux-kernel@vger.kernel.org, Oleg Verych <olecom@flower.upol.cz> Subject: Re: The who needs reviews anyways [PATCH] Date: Fri, 9 Feb 2007 00:20:49 +0100 (CET) [thread overview] Message-ID: <Pine.LNX.4.64.0702090014020.14457@scrub.home> (raw) In-Reply-To: <Pine.LNX.4.64.0702081500190.8424@woody.linux-foundation.org> Hi, On Thu, 8 Feb 2007, Linus Torvalds wrote: > On Thu, 8 Feb 2007, Roman Zippel wrote: > > > I don't quite understand, the Makefile doesn't care anymore about /bin/sh > > with this patch, the Makefile checks only for $BASH and /bin/bash > > Exactly. > > The point is, neither $BASH nor /bin/bash may be set. Is that really a problem? I think any system that has bash without /bin/bash is simply broken. > If you run make while running tcsh, "BASH" won't be set. We've always just > defaulted to doing /bin/sh. Doesn't really seem to be a problem. There are chances this is already broken anyway. We call external scripts using $(shell $(CONFIG_SHELL) ...), which ignores the "#! ..." setting. bye, Roman
next prev parent reply other threads:[~2007-02-08 23:20 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-08 21:48 The who needs reviews anyways [PATCH] Roman Zippel 2007-02-08 22:05 ` Sam Ravnborg 2007-02-08 22:22 ` Linus Torvalds 2007-02-08 22:53 ` Roman Zippel 2007-02-08 23:02 ` Linus Torvalds 2007-02-08 23:20 ` Roman Zippel [this message] 2007-02-09 2:29 ` Valdis.Kletnieks 2007-02-08 23:03 ` Kbuild refactoring (Re: The who needs reviews anyways [PATCH]) Oleg Verych 2007-02-09 0:06 ` The who needs reviews anyways [PATCH] Andreas Schwab 2007-02-09 1:21 ` Roman Zippel 2007-02-09 5:22 ` Oleg Verych 2007-02-09 11:35 ` Roman Zippel 2007-02-09 21:42 ` Oleg Verych
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.64.0702090014020.14457@scrub.home \ --to=zippel@linux-m68k.org \ --cc=linux-kernel@vger.kernel.org \ --cc=olecom@flower.upol.cz \ --cc=torvalds@linux-foundation.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: linkBe 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; as well as URLs for NNTP newsgroup(s).