public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: dash 0.5.11.5
Date: Tue, 21 Sep 2021 11:55:13 -0600	[thread overview]
Message-ID: <04aa78a5-c925-b04f-52aa-69111b919444@Shaw.ca> (raw)
In-Reply-To: <5212e253-7778-f034-d1a9-c4acf0feac40@cornell.edu>

On 2021-09-21 10:58, Ken Brown via Cygwin wrote:
> On 9/21/2021 11:29 AM, Brian Inglis wrote:
>> On 2021-09-20 00:34, ASSI wrote:
>>> Cygwin dash Co-Maintainer writes:
>>>> The following packages have been upgraded in the Cygwin distribution:
>>>>
>>>> * dash    0.5.11.5
>>>
>>> The hint files were touched, but this version is still marked as test.
>>
>> So as previously suggested, and as we discussed trying this when I 
>> upgraded readline, it does appear that we need to bump the release to 
>> get a stable version,
> 
> No, all you have to do is remove the "test:" tags from the hint files.  
> I find the "untest" command to be the simplest way to accomplish this:
> 
>    https://cygwin.com/package-upload.html

Thanks for that pointer.

>> so suggest we mandate release 0 for test versions, as that would 
>> follow naturally.
> 
> There's no need for that.

Maybe it would be a good suggestion then?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2021-09-21 17:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-19 23:27 Cygwin dash Co-Maintainer
2021-09-20  6:34 ` ASSI
2021-09-21 15:29   ` Brian Inglis
2021-09-21 16:58     ` Ken Brown
2021-09-21 17:55       ` Brian Inglis [this message]
2021-09-21 19:12         ` Ken Brown

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=04aa78a5-c925-b04f-52aa-69111b919444@Shaw.ca \
    --to=brian.inglis@shaw.ca \
    --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).