From: Carlos O'Donell <carlos@redhat.com>
To: "Dmitry V. Levin" <ldv@altlinux.org>,
libc-alpha <libc-alpha@sourceware.org>
Subject: Closing branch release/2.27/master?
Date: Mon, 15 Apr 2024 15:01:23 -0400 [thread overview]
Message-ID: <175e3769-e00c-4564-ab3f-20f5dfcb7a48@redhat.com> (raw)
Dmitry,
I was trying to close out branches that we likely no longer want
to support and I noticed ALT p9 went EOL in 2023-12.
Should we close release/2.27/master for support?
Shall we remove "Release/2.27 by Dmitry V. Levin?"
https://sourceware.org/glibc/wiki/Release/
Thank you!
--
Cheers,
Carlos.
next reply other threads:[~2024-04-15 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 19:01 Carlos O'Donell [this message]
2024-04-15 21:39 ` Closing branch release/2.27/master? Dmitry V. Levin
2024-04-17 14:20 ` Carlos O'Donell
2024-04-20 7:16 ` Dmitry V. Levin
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=175e3769-e00c-4564-ab3f-20f5dfcb7a48@redhat.com \
--to=carlos@redhat.com \
--cc=ldv@altlinux.org \
--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).