News for hackers. Stuff that matters.

A comment on Grsecurity: Potential contributory infringement and breach of contract risk. Parent comment

Re:Grsecurity: Potential contributory infringement and breac... by sigjuice on Sunday July 09, 2017 @08:44PM (#14732625)
What is the "extra information" in this context?
[ Parent | on HN ]
Re:Grsecurity: Potential contributory infringement and breac... by mkl on Monday July 10, 2017 @03:38AM (#14734049)
The patch metadata: which lines have changed for what purpose.
[ Parent | on HN ]
Re:Grsecurity: Potential contributory infringement and breac... by sigjuice on Monday July 10, 2017 @04:34AM (#14734243)
Sorry, I am still not sure what you mean. Could you point me at an example of 'patch metadata'? Thanks!
[ Parent | on HN ]
Re:Grsecurity: Potential contributory infringement and breac... by sanxiyn on Monday July 10, 2017 @08:05AM (#14735165)
Here is an example of patch metadata, in this case for Debian: https://anonscm.debian.org/cgit/kernel/linux.git/tree/debian...

"Without patch metadata" would be a single file patch.

[ Parent | on HN ]
Re:Grsecurity: Potential contributory infringement and breac... by sigjuice on Monday July 10, 2017 @02:11PM (#14738305)
Thanks!

A CentOS 6 kernel source rpm that I unpacked recently had multiple patch files in it.

[ Parent | on HN ]