Thread (140 messages) 140 messages, 21 authors, 2018-12-04

Re: [PATCH 14/17] prmem: llist, hlist, both plain and rcu

From: Steven Rostedt <rostedt@goodmis.org>
Date: 2018-10-28 09:52:47
Also in: linux-integrity, lkml

On Wed, 24 Oct 2018 17:03:01 +0300
Igor Stoppa [off-list ref] wrote:
I was hoping that by CC-ing kernel.org, the explicit recipients would 
get both the mail directly intended for them (as subsystem 
maintainers/supporters) and the rest.

The next time I'll err in the opposite direction.
Please don't.
In the meanwhile, please find the whole set here:

https://www.openwall.com/lists/kernel-hardening/2018/10/23/3
Note, it is critical that every change log stands on its own. You do
not need to Cc the entire patch set to everyone. Each patch should have
enough information in it to know exactly what the patch does.

It's OK if each change log has duplicate information from other
patches. The important part is that one should be able to look at the
change log of a specific patch and understand exactly what the patch is
doing.

This is because 5 years from now, if someone does a git blame and comes
up with this commit, they wont have access to the patch series. All
they will have is this single commit log to explain why these changes
were done.

If a change log depends on other commits for context, it is
insufficient.

Thanks,

-- Steve
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help