You don't include attribution at all in the current work. You're not following your own rules (which have no legal basis anyway).
-
-
Replying to @CopperheadOS
nobody includes all the necessry history in every copy either but then that wasn't my question either.
1 reply 0 retweets 0 likes -
Replying to @paxteam
Sure, and the commit messages don't refer to PaX to meet any legal requirements and we don't need to have commit messages at all.
2 replies 0 retweets 1 like -
Replying to @CopperheadOS
which is why i asked who the copyright owner is. git's way of tracking it is the author line, your commit is lying about it.
1 reply 0 retweets 0 likes -
Replying to @paxteam
It isn't lying about anything and no, Git doesn't track copyright. That certainly isn't how it's used by the Linux kernel project. Bullshit.
2 replies 0 retweets 1 like -
Replying to @CopperheadOS @paxteam
This is the relevant documentation, right? https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst#n416 …
2 replies 0 retweets 0 likes -
The condition is that the original source of the code is "indicated in the file", whatever "file" means in that context?
1 reply 0 retweets 0 likes -
Replying to @tehjh @CopperheadOS
some of the relevant parts are quoted in spender's mail earlier today.
1 reply 0 retweets 0 likes -
Replying to @paxteam @CopperheadOS
it seems to me like that's intended for maintainers of subsystems / stable trees, for the case where an existing patch mail is changed?
1 reply 0 retweets 0 likes -
afaics the part above it says that for external GPL'ed code, the origin should be stated "in the file"
2 replies 0 retweets 0 likes
but I'm not sure whether I can unambiguously parse everything in that file
-
-
Replying to @tehjh @CopperheadOS
you should then bring this up on lkml as it's a core document that must be understandable by all potential contributors.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.