X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Date: Sat, 16 May 2009 10:39:07 +0200 From: Spiro Trikaliotis To: cygwin AT cygwin DOT com Message-ID: <20090516083906.GC22639@trikaliotis.net> Mail-Followup-To: cygwin AT cygwin DOT com References: <1242445850 DOT 26068 DOT ezmlm AT cygwin DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-SA-Exim-Connect-IP: 87.163.218.91 X-SA-Exim-Mail-From: an-cygwin AT spiro DOT trikaliotis DOT net Subject: Re: managing autoconf versions? X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000) X-SA-Exim-Scanned: Yes (on mail.trikaliotis.net) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Hello Jay, * On Sat, May 16, 2009 at 06:00:30AM +0000 Jay wrote: > How do people manage autoconf/automake versions? [...] > Rather I'm wondering about submitting patches to other projects, Just make sure you do not include generated files in your patch, and you should be fine. Having the generated files in your patch would produce problems on the other side, regardless if you use the same version of auto* tools or not. HTH, Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/