From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: newlib@sourceware.org
Subject: Re: News outdated and repo needs 3.3.0 tag commit fix
Date: Tue, 3 Oct 2023 16:37:07 -0600 [thread overview]
Message-ID: <33783181-5552-ca7b-f4d5-5adbc79a636a@Shaw.ca> (raw)
In-Reply-To: <CAOox84tPiaZkmbROkFtGdmU1WF+C5FGrrXkdovG3hD5WskWs5A@mail.gmail.com>
Hi Jeff,
The script needs work then ;^> - the tag was attached to the third Cygwin commit
after - almost 14 hours later!
Maybe skip commits where any of the targets are under winsup/?
add pseudo console fixes to release text newlib-3.3.0
[Wed, 22 Jan 2020 10:05:51 +0000 (11:05 +0100)]
...
Bump up newlib release to 3.3.0
[Tue, 21 Jan 2020 20:17:43 +0000 (15:17 -0500)]
Announcement messages are things we sometimes get distracted from by life.
GNU and Cygwin do not always announce every library or package update.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
On 2023-10-03 12:57, Jeff Johnston wrote:
> Thanks for pointing this out. I'll fix the 4.2.0 and 4.3.0 announcements.
>
> Regarding 3.3.0, the tag gets created in the same script I create the
> snapshot so the tag should always match the snapshot. There were
> mitigating circumstances as to why the message wasn't posted, but I'll try
> and not let it happen again.
> On Tue, Oct 3, 2023 at 2:16 PM Brian Inglis wrote:
>> Noticed that News from newlib home page has not been updated for 4.3.0:
>> https://sourceware.org/git/?p=newlib-htdocs.git;a=blob;f=news.html
>> email: newlib-4.3.0 yearly snapshot created
>> https://sourceware.org/pipermail/newlib/2023/020141.html
>> https://inbox.sourceware.org/newlib/CAOox84tjkL4VUHCA5ZQ1FOk0KQv6BTat0XA+RYSHnaYANYdijQ@mail.gmail.com/
>> 4.2.0 lacks the announcement in discussion:
>> https://sourceware.org/pipermail/newlib/2022/019078.html
>> https://inbox.sourceware.org/newlib/CAOox84vpcvdynm2gEvDzS1sC55sp66zMoq_zRCCxidZTsm9hEQ@mail.gmail.com/
>> and there appears to never have been an announcement for 3.3.0,
>> post copyright updates, just the tag newlib-3.3.0:
>> Newlib snapshot for 3.3.0
>> https://sourceware.org/git/?p=newlib-cygwin.git;a=tag;h=b74fcc878149cbf775f2ef12725e9fe48aff7122
>> but that newlib-3.3.0 tag is on a later Cygwin patch rather than:
>> Bump up newlib release to 3.3.0
>> https://sourceware.org/git/?p=newlib-cygwin.git;a=commit;h=4e78f8ea163fec468072e8fe1f498b9abaaf838f
prev parent reply other threads:[~2023-10-03 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 18:15 Brian Inglis
2023-10-03 18:57 ` Jeff Johnston
2023-10-03 22:37 ` Brian Inglis [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=33783181-5552-ca7b-f4d5-5adbc79a636a@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=newlib@sourceware.org \
/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).