DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:cc:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=YKNhxaEIWVuhwRHt
	81cvwV6utArYB+ymuGlPnZcDFtweTITWXtG3EUvrfLmhyEeGO8K0cfM/tJUjwXxT
	yfFtEHIzNqJL1xwquyd3AtBrqzCjNgUQGo9Lh09Uj68TM4I787MjE3thBN1Bf7gI
	CJmpQXKLM0szOqAlGvHgDYz9PiQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Workflow for producing patches with cygport?
To: The Cygwin Mailing List <cygwin@cygwin.com>
References: <59FD9A59.9070201@gmail.com>
Cc: codespunk+cygwin@gmail.com
From: Jon Turney <jon.turney@dronecode.org.uk>
Message-ID: <69ce2531-907d-4c6b-dcb2-fb7ae71251d3@dronecode.org.uk>
Date: Sat, 4 Nov 2017 13:04:19 +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

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