From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 67998 invoked by alias); 4 Nov 2017 13:04:25 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 67989 invoked by uid 89); 4 Nov 2017 13:04:25 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=UD:cygport, prep, package.cygport, UD:package.cygport X-HELO: out4-smtp.messagingengine.com Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 04 Nov 2017 13:04:22 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 021032060A; Sat, 4 Nov 2017 09:04:21 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Sat, 04 Nov 2017 09:04:21 -0400 X-ME-Sender: Received: from [192.168.1.102] (host86-162-230-154.range86-162.btcentralplus.com [86.162.230.154]) by mail.messagingengine.com (Postfix) with ESMTPA id 960A5247AE; Sat, 4 Nov 2017 09:04:20 -0400 (EDT) Subject: Re: Workflow for producing patches with cygport? To: The Cygwin Mailing List References: <59FD9A59.9070201@gmail.com> Cc: codespunk+cygwin@gmail.com From: Jon Turney Message-ID: <69ce2531-907d-4c6b-dcb2-fb7ae71251d3@dronecode.org.uk> Date: Sat, 04 Nov 2017 13:04:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <59FD9A59.9070201@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2017-11/txt/msg00078.txt.bz2 On 04/11/2017 10:45, Matt D. wrote: > I've gotten this far: > >   download cygport >   download package src > >   cd /usr/src/package* >   cygport package.cygport prep > > I can now edit the source, compile, etc. But what is the workflow for > producing a patch file of my changes? You can use 'cygport diff' to produce a patch in ${PN}-${PVR}.${ARCH}/patch/ -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple