From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: libc-alpha@sourceware.org, Siddhesh Poyarekar <siddhesh@sourceware.org>
Cc: carlos@redhat.com, adhemerval.zanella@linaro.org, fweimer@redhat.com
Subject: Re: [PATCH v2] Update advisory format and introduce some automation
Date: Sun, 28 Jan 2024 01:10:32 +0100 [thread overview]
Message-ID: <2667560.X9hSmTKtgW@pinacolada> (raw)
In-Reply-To: <20240124200204.137436-1-siddhesh@sourceware.org>
[-- Attachment #1: Type: text/plain, Size: 791 bytes --]
Am Mittwoch, 24. Januar 2024, 21:02:04 CET schrieb Siddhesh Poyarekar:
> Additionally, the Release wiki needs to be updated to inform the release
> manager to:
>
> 1. Generate a NEWS snipped from the advisories directory
>
> AND
>
> 2. on release/2.YY/master, replace the advisories directory with a text
> file pointing to the advisories directory in master so that we don't
> have to update multiple locations.
Done, feel free to review.
https://sourceware.org/glibc/wiki/Release?action=diff&rev1=241&rev2=242
(The script filenames still need to be fixed after your commit, but I'll go
through the page anyway while doing the release.)
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2024-01-28 0:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 19:58 [PATCH] " Siddhesh Poyarekar
2024-01-24 20:02 ` [PATCH v2] " Siddhesh Poyarekar
2024-01-27 23:54 ` Andreas K. Huettel
2024-01-29 13:55 ` Siddhesh Poyarekar
2024-01-28 0:10 ` Andreas K. Huettel [this message]
2024-01-29 13:56 ` Siddhesh Poyarekar
2024-01-29 13:56 ` [PATCH v3] " Siddhesh Poyarekar
2024-01-30 19:00 ` Siddhesh Poyarekar
2024-01-30 19:02 ` Andreas K. Huettel
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=2667560.X9hSmTKtgW@pinacolada \
--to=dilfridge@gentoo.org \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@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).