lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 16 Dec 2007 20:36:41 -0800 (PST)
From:	David Miller <>
Subject: Re: [PATCH] bridge: assign random address

From: Andrew Morton <>
Date: Sun, 16 Dec 2007 18:55:48 -0800

> Kinda funny.  I (and I bet lots of others) spend a lot of time
> fixing, cleaning up and totally rewriting patch titles.

It's probably the majority of the typing I perform to apply a patch
except for the folks who format things the way that works best for

I realize that I can't get every patch submitter to conform to what I
want, but at least I try to nudge the people who submit the most stuff
to me.

And it's just as much to "help me out" as it is that I want the
changelogs header lines to look consistent.  I'm going to enforce that
consistency anyways. :-)

But if people submit patches in a way that makes life difficult for
the subsystem maintainer, and keeps doing so after being asked to
adjust their submissions a little bit, well... some patches might get
mysteriously ignored.

When you're submitting a lot of patches you're chewing up a LOT of
someone's bandwidth.  I often spend at least 45 minutes a day on
network namespace patches, as one specific example.  That's a large
investment of time to give someone.

In return it's asking very little to "make your subject lines look
like this, it helps me a lot, kthx".

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists