From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: cygport patches for consideration
Date: Tue, 7 Apr 2020 18:14:54 +0100 [thread overview]
Message-ID: <be25243c-a813-3be2-3f7c-c1e245624143@dronecode.org.uk> (raw)
In-Reply-To: <878sj7ck7e.fsf@Rainer.invalid>
On 07/04/2020 17:52, Achim Gratz wrote:
> Yaakov Selkowitz writes:
>
>>> Automatically create a test release if the release string starts with a literal "0"
>>
>> Nak. There is not necessarily any correlation between a -0.* release
>> and whether it should be test or not.
>
> Then there ought to be. :-)
The current package naming guidelines say that a release starting with
'0' should be used for pre-release versions. Those are not necessarily
test versions.
next prev parent reply other threads:[~2020-04-07 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 18:54 Achim Gratz
2020-04-06 14:46 ` Brian Inglis
2020-04-07 0:52 ` Yaakov Selkowitz
2020-04-07 16:52 ` Achim Gratz
2020-04-07 17:14 ` Jon Turney [this message]
2020-04-07 17:37 ` Yaakov Selkowitz
2020-04-07 18:11 ` Achim Gratz
2020-05-10 8:58 ` Achim Gratz
2020-05-10 20:46 ` Yaakov Selkowitz
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=be25243c-a813-3be2-3f7c-c1e245624143@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).