From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from majordomo by infradead.org with local (Exim 3.16 #2) id 13yDX1-0001oe-00 for mtd-list@infradead.org; Tue, 21 Nov 2000 13:32:19 +0000 Received: from cerebus-ext.cygnus.co.uk ([194.130.39.252] helo=passion.cygnus) by infradead.org with esmtp (Exim 3.16 #2) id 13yDX0-0001oY-00 for mtd@infradead.org; Tue, 21 Nov 2000 13:32:18 +0000 From: David Woodhouse In-Reply-To: <01C053BC.A1578B40@smithwicks.softsys.co.at> References: <01C053BC.A1578B40@smithwicks.softsys.co.at> To: Erwin Authried Cc: "'MTD List'" Subject: Re: 2.4 stuff. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Nov 2000 13:32:04 +0000 Message-ID: <27309.974813524@redhat.com> Sender: owner-mtd@infradead.org List-ID: eauth@softsys.co.at said: > Nevertheless, I think that configuration of non-working stuff should > be disallowed by the configuration script, or by aborting the > compilation. Why should we guide the user into a trap if we know it > doesn't work? Agreed. Would it suffice to do this in Config.in for the 2.0 version? -- dwmw2 To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org