public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>, libc-alpha@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: Mon, 29 Jan 2024 08:56:57 -0500	[thread overview]
Message-ID: <74b8c964-3989-4e7a-a9c5-4c7bacce6e1f@sourceware.org> (raw)
In-Reply-To: <2667560.X9hSmTKtgW@pinacolada>

On 2024-01-27 19:10, Andreas K. Huettel wrote:
> 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.)
> 

Perfect, thanks!

Sid

  reply	other threads:[~2024-01-29 13:56 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
2024-01-29 13:56     ` Siddhesh Poyarekar [this message]
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=74b8c964-3989-4e7a-a9c5-4c7bacce6e1f@sourceware.org \
    --to=siddhesh@sourceware.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=dilfridge@gentoo.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@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).