From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITCM] bison dash grep gzip m4 readline sed
Date: Wed, 11 Aug 2021 22:33:30 -0600 [thread overview]
Message-ID: <30469d96-e2ad-a877-1b7b-d52fa9e549be@SystematicSw.ab.ca> (raw)
In-Reply-To: <135aa60f-9b45-9ca8-0cab-ebbcf7eb4681@gmail.com>
On 2021-08-11 14:21, Marco Atzeri via Cygwin-apps wrote:
> On 10.08.2021 07:47, Brian Inglis wrote:
>> Hi folks,
>>
>> Once again been looking over commonly used outdated packages I use
>> frequently which need upgraded and picked another few of Eric Blake's
>> I would like to request to co-maintain and upgrade as they are a few
>> years old.
>>
>> Attn: Eric Blake - advice, comments, concurrence or objections to my
>> co-maintaining the packages for bison dash grep gzip m4 readline sed?
>
> added Eric in CC
BCC?
>> I am as usual dogfooding these, including rerunning the builds and
>> checks after local installs on both arches, but would appreciate any
>> advice about whether any or all of these should be test releases (e.g.
>> readline) before upgrading stable releases (given some recent issues I
>> caused) or other comments or suggestions.
>>
>> These builds have all been tested in the git-cygwin-package playground
>> repo; see:
>>
>> https://cygwin.com/cgi-bin2/jobs.cgi?id=3148..3151,3154-3156
>>
>> commit links show the package and log links show the results.
>>
>> [I am working up to looking at dealing with bash and/or coreutils: any
>> suggestions for less significant packages to tackle for more
>> experience upgrading packages needing Cygwin tweaks would be welcome!
>> ;^>]
>
> I assume the previous answer from Eric is also valid here
> so I added Brian as co-maintainer
Thanks Marco
I will push each package's updated .cygport to init each package's
git-cygwin-package repo, on the playground branch, so builds can be
reviewed, and any feedback or suggestions given, as these packages'
functioning are fairly core and some are Base packages required in all
Cygwin installations.
--
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.]
next prev parent reply other threads:[~2021-08-12 4:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 5:47 Brian Inglis
2021-08-11 20:21 ` Marco Atzeri
2021-08-12 4:33 ` Brian Inglis [this message]
2021-08-12 6:54 ` Marco Atzeri
2021-08-12 16:13 ` Brian Inglis
2021-08-13 3:26 ` Brian Inglis
2021-09-08 18:59 ` [ITCM] patchutils Brian Inglis
2021-09-10 19:13 ` Marco Atzeri
2021-09-11 1:54 ` Brian Inglis
2021-09-11 2:25 ` patchutils package builds for review Brian Inglis
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=30469d96-e2ad-a877-1b7b-d52fa9e549be@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).