From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH cygport] Write and upload pvr.hint rather than setup.hint
Date: Fri, 16 Sep 2016 19:47:00 -0000 [thread overview]
Message-ID: <5bd070a1-6b95-b120-4522-2642c9213d11@cygwin.com> (raw)
In-Reply-To: <6706945e-ca9a-af88-cd69-92239ae243d3@dronecode.org.uk>
On 2016-09-01 12:12, Jon Turney wrote:
> On 30/08/2016 13:24, Jon Turney wrote:
>> For a source-only package, rather than just a skip: key, write category:,
>> requires:, ldesc: and sdesc: keys as well.
>
> This had a rather unfortunate bug which made it always generate a
> source-only package hint (i.e. with skip:), rather than only when needed
> because nothing else has generated the package hint.
>
> Updated version attached.
Merged and pushed.
--
Yaakov
prev parent reply other threads:[~2016-09-16 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 12:25 Jon Turney
2016-09-01 17:12 ` Jon Turney
2016-09-16 19:47 ` Yaakov Selkowitz [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=5bd070a1-6b95-b120-4522-2642c9213d11@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-apps@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).