From mint-bounce@lists.fishpool.fi Wed Jan 28 10:03:08 2009 Date: Wed, 28 Jan 2009 16:00:58 +0100 (CET) From: Frank Naumann X-X-Sender: fnaumann@localhost.localdomain To: Alan Hourihane Cc: Mint list Subject: Re: [MiNT] mintlib-enhancements In-Reply-To: <1233154017.26613.6.camel@jetpack.demon.co.uk> Message-ID: References: <1233136575.26613.0.camel@jetpack.demon.co.uk> <1233151160.26613.4.camel@jetpack.demon.co.uk> <1233154017.26613.6.camel@jetpack.demon.co.uk> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=- tagged_above=-50.5 required=7.0 WHITELISTED X-Spam-Level: X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: fnaumann@boerde.de Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Hello! >> For mintlib sure. As the mintlib is used only by developers anyway we >> don't need a special tag for testing (for the kernel this is a different >> thing; critical changes shall be well tested before they are widely used). > > Some of the commits I'm about to make to mintlib require an updated > kernel though. > > Should I commit those to the trunk as well ? Sure. This also allow testing of the mintlib changes on older kernels too. Regards, Frank -- ATARI FALCON 060 // MILAN 060 ----------------------------- http://sparemint.org/ e-Mail: fnaumann@boerde.de