Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 28 Oct 2018 05:52:33 -0400
From: Steven Rostedt <>
To: Igor Stoppa <>
Cc: Mathieu Desnoyers <>, Mimi Zohar
 <>, Kees Cook <>, Matthew
 Wilcox <>, Dave Chinner <>, James
 Morris <>, Michal Hocko <>,,,, igor stoppa
 <>, Dave Hansen <>,
 Jonathan Corbet <>, Laura Abbott <>, Thomas
 Gleixner <>, Kate Stewart <>,
 "David S. Miller" <>, Greg Kroah-Hartman
 <>, Philippe Ombredanne <>,
 "Paul E. McKenney" <>, Josh Triplett
 <>, Lai Jiangshan <>,
 linux-kernel <>
Subject: Re: [PATCH 14/17] prmem: llist, hlist, both plain and rcu

On Wed, 24 Oct 2018 17:03:01 +0300
Igor Stoppa <> wrote:

> I was hoping that by CC-ing, 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:

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

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


-- Steve

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.