From mint-bounce@lists.fishpool.fi Sun Aug 15 12:35:09 2010 X-Virus-Scanned: amavisd-new at demon.co.uk Subject: Re: [MiNT] Set of patches for current release From: Alan Hourihane To: Miro Kropacek Cc: MiNT Mailing List In-Reply-To: References: <1281828578.27932.4.camel@jetpack.demon.co.uk> <1281871860.4211.3.camel@jetpack.demon.co.uk> Content-Type: text/plain; charset="us-ascii" Date: Sun, 15 Aug 2010 17:32:03 +0100 Message-ID: <1281889923.4211.5.camel@jetpack.demon.co.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.30.2 Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: alanh@fairlite.co.uk Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: On Sun, 2010-08-15 at 13:45 +0200, Miro Kropacek wrote: > > Then update the Makefiles. > Too much work for me ATM :( O.k. > > I certainly don't want to modify Makefiles like this. You might as well > > shift the entire diff to a separate shell script instead and we can > > commit a new file. > I have absolutely no problem with this solution. My goal was to make > quick release tree, not showing how cool I am in shell scripting or > how clean patches I'm able to deliver. > > Are you going to provide output of my script on your server so others > can review / comment it? I don't care about a form, really, I just > wanted to make a release more user friendly, nothing more. Sure I'd do it if it were in a shell script. I'm just not committing the Makefile changes. Alan.