public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
* Announcing backports on libc-stable
@ 2021-09-17 10:13 Florian Weimer
  2021-09-20  5:49 ` Siddhesh Poyarekar
  2021-09-21  0:59 ` Dmitry V. Levin
  0 siblings, 2 replies; 3+ messages in thread
From: Florian Weimer @ 2021-09-17 10:13 UTC (permalink / raw)
  To: libc-alpha, libc-stable

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.

Thanks,
Florian


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Announcing backports on libc-stable
  2021-09-17 10:13 Announcing backports on libc-stable Florian Weimer
@ 2021-09-20  5:49 ` Siddhesh Poyarekar
  2021-09-21  0:59 ` Dmitry V. Levin
  1 sibling, 0 replies; 3+ messages in thread
From: Siddhesh Poyarekar @ 2021-09-20  5:49 UTC (permalink / raw)
  To: Florian Weimer, libc-alpha, libc-stable

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Announcing backports on libc-stable
  2021-09-17 10:13 Announcing backports on libc-stable Florian Weimer
  2021-09-20  5:49 ` Siddhesh Poyarekar
@ 2021-09-21  0:59 ` Dmitry V. Levin
  1 sibling, 0 replies; 3+ messages in thread
From: Dmitry V. Levin @ 2021-09-21  0:59 UTC (permalink / raw)
  To: libc-alpha, libc-stable

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
libc-stable.


-- 
ldv

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-09-21  0:59 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-09-17 10:13 Announcing backports on libc-stable Florian Weimer
2021-09-20  5:49 ` Siddhesh Poyarekar
2021-09-21  0:59 ` Dmitry V. Levin

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