On Fri, Nov 14, 2008 at 22:33, Martin Koegler <mkoegler@xxxxxxxxxxxxxxxxx> wrote: > On Fri, Nov 14, 2008 at 09:59:56PM +0100, Andreas Ericsson wrote: >> I've put everyone who "owns" more than 500 lines of code >> on the bcc list, figuring your permission is important >> but that you don't want the hundreds (well, one can hope) >> of emails from people saying "ok". The list of major owners >> was generated with "git showners *.c" in a worktree from >> the next branch of git.git. > > I don't think, that your way for relicensing is bullet proof: > > I consider many of my GIT patches as derived work from other parts of > GIT, even if git blame is stating me as author. I can gurantee you, > that I comply with the "Developer's Certificate of Origin 1.1" point > b, as its based on code out of git.git. But I can't tell you, from > which files I reused code anymore. > > Probably other people did the same. > > Your method is ignoring such derived code. Perhaps git stats can be of assistance here, it can summarize how much lines a person changed (per file, or in total), that should be a better metric (at least for code reused from within git.git, ofcourse GPL-ed code taken from somewhere else is not covered). -- Cheers, Sverre Rabbelier -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
