lists.openwall.net   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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 25 Mar 2009 09:58:52 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	LKML <linux-kernel@...r.kernel.org>
cc:	Frédéric Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Credit for vsprintk work


Frederic,

 $ git blame lib/vsprintf.c |grep 'Frederic Weisbecker' | wc -l
542

You did a hell of a lot of work on vsprintf.c, and you are still too 
modest to put in a copyright at the top.

I know some people think that git is good enough for ownership. But 
really, the amount of changes that you did in vsprintf.c deserves a bit of 
credit in the source file.

Is everyone OK if a copyright goes at the top of this file giving credit 
to Frederic?  If for anything else, it will facilitate people to find who 
broke it if it breaks ;-)

I think Frederic should send one more patch to add his copyright. That is, 
of course, if Frederic wants too.

Note, Frederic did not ask me to post this. In fact, this is the first 
time he's seen this complaint. I'm posting this because I was showing this 
code to some students at a University and when I wanted to point out 
who wrote it, I was surprised that Frederic's name was not mentioned.
I was looking at the code via LXR so git was not helpful here.

-- Steve

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ