Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <00bd01c2e5d9$667012c0$78d96f83@pomello> From: "Max Bowsher" To: "Cygwin \(Robert Collins\)" , References: <006e01c2caf4$8e290880$78d96f83 AT pomello> <008a01c2e5d8$cfaa0d00$0400a8c0 AT robertcollins DOT net> Subject: Re: Removing concat.cc/h Date: Sun, 9 Mar 2003 01:15:40 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Cygwin (Robert Collins) wrote: > === > ----- Original Message ----- > From: "Max Bowsher" > > >> What is policy for setup? Should we regenerate Makefile.in (and >> aclocal.m4, and any other relevent files) with the current Cygwin >> release of automake, since we are changing it at all, or would you >> prefer to keep it at the version currently used? > > The policy is: > Whatever version a maintainer has when committing is what goes into > CVS. Patches must be sent without such cruft to be applied. > > This obviously gets easier if we remove said files from CVS. Then lets wait until the week you allocated for objections to the above removal is up, before worrying further about this. Do you approve the removal of concat.* once the generated files have been removed? Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/