X-Recipient:	archive-cygwin AT delorie DOT com
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=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=6MsxVhJtO6JakWfYKCdWch
	ThATQ=; b=fiP1lrTPkPdOAtQQRXkwA2Tqzsmqxry1dQB45xNaIPR22Okey+7nkK
	8r/wzLpKOiDt/zJa6dNtTVXOKfquVEfn5BQD5mVK2ZCo+YuV41PFasi26MNfM7H2
	swyGRTMSLUNEkr5V9LuHSbKy8DZif5aj/7ODaBn8ov+Ucj/vsb3cQ=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
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
X-ME-Sender:	<xms:1Lr9WYS8zknYQeFUrsQ8v4pSyEJByh4cstdydlydeUNi-Nh5PLUM6Q>
Subject:	Re: Workflow for producing patches with cygport?
To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
References:	<59FD9A59 DOT 9070201 AT gmail DOT com>
Cc:	codespunk+cygwin AT gmail DOT com
From:	Jon Turney <jon DOT turney AT dronecode DOT org DOT 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>

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

- Raw text -