public inbox for
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <>
Subject: Re: Announcing backports on libc-stable
Date: Tue, 21 Sep 2021 03:59:57 +0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Sep 17, 2021 at 12:13:15PM +0200, 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 agree, manual postings to libc-stable of pushed commits seem to be a
waste of time.  I've just pushed a few backports to release/2.27/master
branch, please let me know if you want them to be posted manually to


      parent reply	other threads:[~2021-09-21  0:59 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
2021-09-21  0:59 ` Dmitry V. Levin [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).