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:reply-to:to:subject:message-id:date
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=b9mA/weR9SdAcNrYXlh1W0Ayb9Sb+SXeJv094k2Ko6E+4KZme6/X9
	rpj4YxVO1SpSif0JSuHoLbTBMBzyePEcY4ITVq2bMPgkNBrkXRua1+jtuTIjr7jl
	Ao1Ca0w5Xq/htt/ESrW1PKQrtaVAnaS5vBOHbIFUpSVxX8IGlOzaBs=
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:reply-to:to:subject:message-id:date
	:mime-version:content-type:content-transfer-encoding; s=default;
	bh=ID4gUWFYGYSquFcjuUihHqd9OKU=; b=CHVBoWrwYMgT3vJJzlw1TFUxW/cc
	Ld7OIWRjxw2AflNJKcSTYu2Vr0AqXM/XrtU5jfLgWajkz1hkON9I8sf4yDKWxds1
	kzMIsruof7nGijpvuqFWiSuNvJQdvi6r9yN2Wt7hjhdO/XyJ+woc2n9Me7OQA3kG
	hDsLomPWB0v/9ZQ=
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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,FREEMAIL_REPLYTO,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=
X-HELO:	mail-pf0-f173.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:reply-to:to:subject:message-id:date :user-agent:mime-version:content-transfer-encoding; bh=Q8IBIrnl+w0k9YOUyBCedbqYMUy68Gz9598KwMIfJYA=; b=MlY0e+RZiAzvSfMPyeMU+3z14Y/VmQpnVoZ2agK60oUuu2HCgCUrB4M/GLEv+Wl7sS E/SvUcfDRMuLlXWOdpCIX9T/Sz/NWt1DDSBVYjLbaJ1vPvH70jY/OKRxNjXs5ueC8uLh lHKCHWES1ReU43Ef4aM923ta0lyY++5AbaF/3e+I+AgEC2JCCyx97ccy3OUBO7yZNwJT l0T9Q7SDzwK8f9MnOhWdXDTBeftcci4dyHZyWGtJDokoZH4+QTCJvBA2mFM0ox9G7tUL fd76F/CanOFxO0MCtk2YwQST/44g5r5PlbH2DRmN9LvfA0rlHKVQjdvM397RNyh0thrY HLnw==
X-Gm-Message-State:	AMCzsaWywW3VnOTsELAk2ez/nJmbpJ/7tKVF7E137+hH1uahYylXSgwY OvnlJc7jwgapbiZomdDoMT0yqC7X
X-Google-Smtp-Source:	ABhQp+TeXxql3oznyaDwyGpWXMLCX76pMor8/DUh0YqhugbYlWK2l37pUH9p3V3o900qYTzMEIIldg==
X-Received:	by 10.98.20.197 with SMTP id 188mr10472483pfu.94.1509792341013; Sat, 04 Nov 2017 03:45:41 -0700 (PDT)
From:	"Matt D." <codespunk AT gmail DOT com>
X-Google-Original-From:	"Matt D." <codespunk+cygwin AT gmail DOT com>
Reply-To:	codespunk+cygwin AT gmail DOT com
To:	cygwin AT cygwin DOT com
Subject:	Workflow for producing patches with cygport?
Message-ID:	<59FD9A59.9070201@gmail.com>
Date:	Sat, 4 Nov 2017 06:45:45 -0400
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version:	1.0

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?


Matt D.

--
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 -