From: Joel Brobecker <brobecker@adacore.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: cti-tac@lists.linuxfoundation.org,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: Next steps from GTI TAC meeting on 2023-03-08 - Evaluate cost of glibc migration.
Date: Mon, 22 May 2023 03:11:21 -0700 [thread overview]
Message-ID: <ZGs/yahtWK4pholh@adacore.com> (raw)
In-Reply-To: <2938fae6-fc5-67e4-d85-3f193b68da89@codesourcery.com>
> > * Sending per-commit email to mailing lists -- this seems like a vestigial
> > feature from the pre-git past. Does it really serve any purpose? I am
> > fighting to kill a similar feature used on the kernel.org side, because I do
> > not see any remaining legitimate use for it -- it just creates a lot of mail
> > traffic that nobody really reviews.
>
> I think it's extremely useful to have those messages for watching out for
> commits that shouldn't have gone in or went in in an unintended form (this
> is for human-determined "shouldn't" or "unintended" - not anything
> expected to be covered by automated checks). And also to have a message
> ready-made to reply to when something was committed without being posted
> to the mailing list.
I strongly agree as well.
--
Joel
next prev parent reply other threads:[~2023-05-22 10:11 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 22:47 Next steps from GTI TAC meeting on 2023-03-08 - Evaluate cost of glibc migration Joseph Myers
2023-05-22 10:11 ` Joel Brobecker [this message]
2023-05-24 12:44 ` Carlos O'Donell
2023-05-24 13:43 ` Siddhesh Poyarekar
2023-05-24 14:12 ` Carlos O'Donell
2023-05-24 15:18 ` Siddhesh Poyarekar
2023-05-23 17:38 ` Konstantin Ryabitsev
2023-05-23 19:34 ` Joseph Myers
2023-05-23 19:52 ` Konstantin Ryabitsev
2023-05-23 20:12 ` Joseph Myers
2023-05-23 20:21 ` Konstantin Ryabitsev
2023-05-23 22:12 ` Joseph Myers
2023-05-24 16:29 ` Konstantin Ryabitsev
2023-05-24 18:13 ` Siddhesh Poyarekar
2023-05-24 18:55 ` Brian Behlendorf
2023-05-24 21:27 ` Siddhesh Poyarekar
2023-05-25 11:06 ` Carlos O'Donell
2023-05-24 19:06 ` Konstantin Ryabitsev
2023-05-24 19:42 ` Joseph Myers
2023-05-24 21:12 ` Siddhesh Poyarekar
2023-05-25 11:12 ` Carlos O'Donell
2023-05-24 18:58 ` Joseph Myers
2023-05-24 12:11 ` Siddhesh Poyarekar
2023-05-24 18:44 ` Joseph Myers
2023-05-24 19:58 ` Carlos O'Donell
2023-05-24 12:57 ` Carlos O'Donell
2023-05-24 18:46 ` Joseph Myers
2023-05-24 20:19 ` Carlos O'Donell
2023-05-24 20:48 ` Joseph Myers
-- strict thread matches above, loose matches on Subject: below --
2023-04-03 17:24 Carlos O'Donell
2023-04-12 20:46 ` Konstantin Ryabitsev
2023-04-12 21:28 ` Brian Behlendorf
2023-05-19 21:00 ` Konstantin Ryabitsev
2023-05-22 14:37 ` Ian Kelling
2023-05-24 20:50 ` Carlos O'Donell
2023-05-24 21:53 ` Ian Kelling
2023-05-25 11:02 ` Carlos O'Donell
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=ZGs/yahtWK4pholh@adacore.com \
--to=brobecker@adacore.com \
--cc=cti-tac@lists.linuxfoundation.org \
--cc=joseph@codesourcery.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.