From mint-bounce@lists.fishpool.fi Sat May 23 08:44:08 2009 Message-ID: <4A17EF15.105@freesbee.fr> Date: Sat, 23 May 2009 14:41:57 +0200 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: mint CC: Frank Naumann Subject: Re: [MiNT] osbind.S ? References: <4A129EFA.8020401@freesbee.fr> <4A15702A.6010108@freesbee.fr> <4A16B68F.1090105@freesbee.fr> <4A1708C1.5080403@freesbee.fr> < <4A17A69E.1090702@freesbee.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Antivirus: avast! (VPS 090522-0, 22/05/2009), Outbound message X-Antivirus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id n4NCi8qw013577 Frank Naumann wrote: >> However, it would >> probably be good to split syscalls.master into osbind.master, >> mintbind.master, and so on. > > No, the main idea behind the master file is to have *one* master file. > We can for sure generate an obsind.h, mintbind.h and so on if you like. > I just see no reason for that. So let's keep only one master file. We could split it later if some good reason appears. -- Vincent Rivière