CIRCLE WITH A DOT

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

And when you make changes to 20,000 kmalloc calls, you start getting CCed on a LOT of patches since you touched "neighboring code" recently.

8 Posts 6 Posters 0 Views

K This user is from outside of this forum
K This user is from outside of this forum
kees@hachyderm.io

wrote last edited by

#1

RE: https://fedi.lwn.net/@lwn/116239303710146388
And when you make changes to 20,000 kmalloc calls, you start getting CCed on a LOT of patches since you touched "neighboring code" recently.
T C E J 4 Replies Last reply
1
0
K kees@hachyderm.io

RE: https://fedi.lwn.net/@lwn/116239303710146388
And when you make changes to 20,000 kmalloc calls, you start getting CCed on a LOT of patches since you touched "neighboring code" recently.
T This user is from outside of this forum
T This user is from outside of this forum
ted@social.gould.cx

wrote last edited by

#2

@kees teach you to try and make things better
1 Reply Last reply

0
K kees@hachyderm.io

RE: https://fedi.lwn.net/@lwn/116239303710146388
And when you make changes to 20,000 kmalloc calls, you start getting CCed on a LOT of patches since you touched "neighboring code" recently.
C This user is from outside of this forum
C This user is from outside of this forum
corbet@social.kernel.org

wrote last edited by

#3

@kees Gee, sounds like being the docs maintainer
1 Reply Last reply

0
K kees@hachyderm.io

RE: https://fedi.lwn.net/@lwn/116239303710146388
And when you make changes to 20,000 kmalloc calls, you start getting CCed on a LOT of patches since you touched "neighboring code" recently.
E This user is from outside of this forum
E This user is from outside of this forum
ermo@fosstodon.org

wrote last edited by

#4

@kees Oof.
1 Reply Last reply

0
K kees@hachyderm.io

RE: https://fedi.lwn.net/@lwn/116239303710146388
And when you make changes to 20,000 kmalloc calls, you start getting CCed on a LOT of patches since you touched "neighboring code" recently.
J This user is from outside of this forum
J This user is from outside of this forum
jani@floss.social

wrote last edited by

#5

@kees I'm eagerly waiting for your upcoming patches to get_maintainer.pl next.
1 Reply Last reply

0
R relay@relay.infosec.exchange shared this topic
J This user is from outside of this forum
J This user is from outside of this forum
jani@floss.social

wrote last edited by

#6

@ljs @kees
Yeah, returning stuff from git history should only be a fallback for files without maintainers. I get my fair share of these Cc's and I'm always like WTF why am I included.
IMO it should also only include the most specific maintainers by default. If you have the maintainer for file foo/bar/baz, don't include the maintainer for foo/bar or foo.
J 1 Reply Last reply

0
J jani@floss.social

@ljs @kees
Yeah, returning stuff from git history should only be a fallback for files without maintainers. I get my fair share of these Cc's and I'm always like WTF why am I included.
IMO it should also only include the most specific maintainers by default. If you have the maintainer for file foo/bar/baz, don't include the maintainer for foo/bar or foo.
J This user is from outside of this forum
J This user is from outside of this forum
jani@floss.social

wrote last edited by

#7

@ljs @kees
Oh, and the primary reason I only whine and moan here instead of sending patches is that the damn thing is written in Perl. Plus I don't want to get Cc'd for patches touching get_maintainer.pl in the future. No wait.
1 Reply Last reply

0
P This user is from outside of this forum
P This user is from outside of this forum
ptesarik@infosec.exchange

wrote last edited by

#8

@ljs @jani @kees @vbabka Ugh, why is this still written in Perl?
Why didn't someone rewrite it in—I don't know—Brainfuck?
1 Reply Last reply
1
0

Log in to reply