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:from:subject:reply-to:references:to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=oEQMCJ1/4/uBDaHh
	maM6SoIIU+8mXsuIivTzFl3N9+XJLqExCxw+mR07XAt2jMDj03wBaPG1n51wUwcL
	TmDSN0a0DFuEZiiZHUkUPtBKNuMJdZVWq5C5SgEvRfWteYaUY33ICjWnFFhawJdT
	R27Ew0U0Ge1ngof6IOlY+twBmlg=
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:from:subject:reply-to:references:to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=GIy4npxDeJXAwi7k+KwVHg
	s/QHY=; b=aztedEXaynZWbnJFdmLTY1eUcHZRAk0uPWrO13287noRmO4aLyRLsT
	MnRkMLja3G4coZzqrrEn4jc69EMbD979l63A2zGvLL6HmdgU5sR1wUl4Ybg1YJ9a
	LaJn8QU4ORa/rzfb7DNbbzllfEj7cnSqdzLr+mI7uASE9ZpFWXek8=
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=-0.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,FREEMAIL_REPLYTO,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=
X-HELO:	mail-pf0-f179.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:reply-to:references:to:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=PjU1IFre/XeVC/9CIe3Ii9dXALNZYvOEakYqVtOR7uM=; b=POmIlSe9ctezmWa71ExEtcmY/LpU8H+SQ7lg0DpT9jW4ho99jTumek74mZmoQrGxUV VO5csgJrT+O1C1Gwv/LDFK1Sv9bu+26h/nB0YAG6rgYGz6FrwsS3wHD4CT/Dtbuo/LpU wSDs00d4tSJwL7G2FecXF080xBMgopHPXkZbLtLluutAA5CYNEB7vPmvhG/Xp2UmIHHz X1edQZR1UwGvt7ngxY8L77AtrN4wVHjmauamVQPiCBLeIsVEp2p0Nk7ZZ9aR/vdKa+86 9Kl4uiDiJWJR942bWJjP9L9bn828e8weCig9YrJiZORO/IWhKSZOH4jsnqfUPxhVquPh 4/+w==
X-Gm-Message-State:	AMCzsaWHzdk5Xrz7PPEW4V9gNeifdJB0jgk7/FJwpLygsIfYhoyUCLRU yzzsW8ninChXQSVkUDJTv4686RRe
X-Google-Smtp-Source:	ABhQp+SZtzT6Hhg6xATkz3fEvlCLNiHzl4sm7JoyCviprU32a9kzbEpcsV3lmFgVJ3/Gt0bdxc2ygA==
X-Received:	by 10.159.249.9 with SMTP id bf9mr9788671plb.383.1509802166776; Sat, 04 Nov 2017 06:29:26 -0700 (PDT)
From:	"Matt D." <codespunk AT gmail DOT com>
X-Google-Original-From:	"Matt D." <codespunk+cygwin AT gmail DOT com>
Subject:	Re: Workflow for producing patches with cygport?
Reply-To:	codespunk+cygwin AT gmail DOT com
References:	<59FD9A59 DOT 9070201 AT gmail DOT com> <69ce2531-907d-4c6b-dcb2-fb7ae71251d3 AT dronecode DOT org DOT uk>
To:	cygwin AT cygwin DOT com
Message-ID:	<59FDC0B5.1060703@gmail.com>
Date:	Sat, 4 Nov 2017 09:29:25 -0400
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version:	1.0
In-Reply-To:	<69ce2531-907d-4c6b-dcb2-fb7ae71251d3@dronecode.org.uk>

Thank you.

There is no documentation for this from 'cygport --help' or 'man 
cygport'. Is this an oversight?


Matt D.

On 11/4/2017 9:04 AM, Jon Turney wrote:
> 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 -