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 Date: Fri, 22 Mar 2002 09:24:07 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Strange behaviour of vpath with dos paths Message-ID: <20020322142407.GD20338@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3C7D11A2 DOT 8070202 AT s3group DOT com> <3C9A058D DOT FFABFA63 AT csksoftware DOT com> <20020321192615 DOT GO14885 AT redhat DOT com> <3C9B0614 DOT A05EBE8D AT csksoftware DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C9B0614.A05EBE8D@csksoftware.com> User-Agent: Mutt/1.3.23.1i On Fri, Mar 22, 2002 at 11:23:16AM +0100, Johan Bezem wrote: >Christopher Faylor wrote: > >> >So, my question: Where can I find the repository of the CygWin make >> >package? Or otherwise, how to proceed from here? >> >> You can't. Use the make source tarball and submit ChangeLog + patch >> here. > >OK, here it goes. I'm not aware of standard testing procedures or >requirements for CygWin, so maybe someone could double-check. > >I used > diff -up .orig.c .c > .c-patch 2>&1 >for both vpath.c and read.c, files attached. You can use the standard procedures outlined at the contrib link at http://cygwin.com./ . That means you send the ChangeLog entry (not the diff of a ChangeLog entry) and patch in clear text so that the barrier to inspecting your work is minimal. This is standard across every project that I am aware of. cgf -- 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/