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  linux-hardening  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, 12 Oct 2014 10:32:01 -0400
From:	Linus Torvalds <>
To:	James Morris <>, Paul Moore <>
Cc:	LSM List <>,
	Linux Kernel Mailing List <>,
	Stephen Rothwell <>
Subject: Re: [GIT] Security subsystem upate for 3.18

On Sun, Oct 12, 2014 at 10:12 AM, Linus Torvalds
<> wrote:
> Give me a synopsis of what has changed and why I should pull.

Side note: this is not just for me personally (so that I have a better
overview of what is going on during the merge window), but also so
that I can make sure that my merge messages are informative and tell
people what I merged and why.

In a perfect world, people could just read my merge messages and get a
good overview of everything that has changed. But that depends on
maintainers giving me those nice summaries of what the big important
changes have been for that merge. I can, and occasionally do, try to
write something up myself, but quite frankly, subsystem maintainers
are just *so* much better positioned to give a good summary of what
has been going on, that I really want that.

Of course, sometimes the summary might just be "a few trivial fixes"
and then people who really want the details can just look at the
individual commits. At other times, maybe you'd want to go into more
detail about some subtle change. There's no fixed format, but it's
supposed to be a human-readable quick high-level overview of what the
merge brings in.

You can just do "git log --author=Torvalds --merges" to see examples
of what people send me. Some people explain more, some explain less, I
really don't have any hard requirements. But I do want to get *some*

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists