On Wed, Jun 17, 2026 at 05:03:52PM +0200, Casey Connolly wrote: > Hi Tom, > > On 16/06/2026 16:36, Tom Rini wrote: > > On Tue, Jun 16, 2026 at 03:11:26PM +0200, Casey Connolly wrote: > > > >> Their email is no longer valid and bounces, ensure we don't include it > >> in get_maintainer.pl output. > >> > >> Signed-off-by: Casey Connolly <[email protected]> > >> --- > >> .get_maintainer.ignore | 1 + > >> 1 file changed, 1 insertion(+) > >> > >> diff --git a/.get_maintainer.ignore b/.get_maintainer.ignore > >> index 899a1469b2ae..5b7d84646f62 100644 > >> --- a/.get_maintainer.ignore > >> +++ b/.get_maintainer.ignore > >> @@ -1 +1,2 @@ > >> "Pali Rohár" <[email protected]> > >> +Tingting Meng <[email protected]> > > > > The .get_maintainer.ignore file is a heavy-handed measure for things > > more serious than just bouncing email. It looks like Tingting Meng just > > comes up via git history and so will roll out of emails in a few months > > now, so I don't want to go this path. > > Ok, that makes sense. I have found bouncing emails and excessively long > CC lists to be a bit of a recurring email when using b4 prep > --auto-to-cc, do you have any ideas on how we can improve this? > > Maybe we could tighten the timeline and/or contribution weight a bit?
It's hard because we've had contributors at both ends of the spectrum speak up before. I think what Marek has been doing to use "N" to get more files covered by maintainers directly helps so that more things will always have someone else see them and in the future maybe we can try and lower the git range. -- Tom
signature.asc
Description: PGP signature
