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 13yDoj-0001rW-00 for mtd-list@infradead.org; Tue, 21 Nov 2000 13:50:37 +0000 Received: from www.softsys.co.at ([194.152.163.161] helo=corofin.softsys.co.at ident=qmailr) by infradead.org with smtp (Exim 3.16 #2) id 13yDod-0001rQ-00 for mtd@infradead.org; Tue, 21 Nov 2000 13:50:32 +0000 Message-ID: <01C053C9.CA6DCFA0@smithwicks.softsys.co.at> From: Erwin Authried To: 'MTD List' Subject: Re: 2.4 stuff. Date: Tue, 21 Nov 2000 14:46:10 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-mtd@infradead.org List-ID: David Woodhouse[SMTP:dwmw2@infradead.org] wrote: > > 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? > I'm not sure about 2.2, but I believe all the module related stuff is working there. At least, we shouldn't care about 2.1. -Erwin To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org