From: "Matt D." <codespunk@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Workflow for producing patches with cygport?
Date: Sat, 04 Nov 2017 13:29:00 -0000 [thread overview]
Message-ID: <59FDC0B5.1060703@gmail.com> (raw)
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
prev parent reply other threads:[~2017-11-04 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 10:45 Matt D.
2017-11-04 13:04 ` Jon Turney
2017-11-04 13:29 ` Matt D. [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59FDC0B5.1060703@gmail.com \
--to=codespunk@gmail.com \
--cc=codespunk+cygwin@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).