From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Florian Weimer <fweimer@redhat.com>,
libc-alpha@sourceware.org, libc-stable@sourceware.org
Subject: Re: Announcing backports on libc-stable
Date: Mon, 20 Sep 2021 11:19:40 +0530 [thread overview]
Message-ID: <ae644a26-65d1-8a14-9be2-17b4c26bb7f7@gotplt.org> (raw)
In-Reply-To: <87y27vechw.fsf@oldenburg.str.redhat.com>
On 9/17/21 15:43, Florian Weimer via Libc-alpha wrote:
> Currently, we say that backported commits should be posted to
> libc-stable.
>
> Is there really any value in doing this?
>
> The glibc-cvs commit notifications are regular enough and can be
> filtered down to stable branches if people are interested in that.
I won't complain if libc-stable were to be retired or we simply had
glibc-cvs redirect release/[0-9\.]+/master commits to it. That will
reduce the busy work.
Siddhesh
next prev parent reply other threads:[~2021-09-20 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 10:13 Florian Weimer
2021-09-20 5:49 ` Siddhesh Poyarekar [this message]
2021-09-21 0:59 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae644a26-65d1-8a14-9be2-17b4c26bb7f7@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-stable@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).