1 |
On Wed, Nov 14, 2018 at 6:45 AM Andrew Savchenko <bircoph@g.o> wrote: |
2 |
> |
3 |
> On Wed, 14 Nov 2018 07:50:48 -0800 Rich Freeman wrote: |
4 |
> > On Tue, Nov 13, 2018 at 6:46 PM William Hubbs <williamh@g.o> wrote: |
5 |
> > > |
6 |
> > > On Tue, Nov 13, 2018 at 06:17:17PM -0800, Rich Freeman wrote: |
7 |
> > > > On Tue, Nov 13, 2018 at 10:32 AM William Hubbs <williamh@g.o> wrote: |
8 |
> > > > > |
9 |
> > |
10 |
> > Give me an example of a Linux kernel source file that contains a |
11 |
> > multiline table of years and copyright holders. At best you'll find |
12 |
> > random notices scattered around files in my experience, mostly because |
13 |
> > of how the code was pulled in from outside. |
14 |
> |
15 |
> Sure, from line 4 to line 10: |
16 |
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/char/random.c |
17 |
> |
18 |
> Multiline table with copyright holders and separate years for each |
19 |
> one. |
20 |
|
21 |
Sure, now look at the very next file in the same directory: |
22 |
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/char/raw.c |
23 |
|
24 |
No copyright notice at all. |
25 |
|
26 |
As I said, you'll find random notices scattered at various places. |
27 |
Sometimes they are more consecutive than others, probably more due to |
28 |
wherever they were borrowed from. |
29 |
|
30 |
> |
31 |
> > > Look anywhere outside the Gentoo tree. For that matter, take the Linux |
32 |
> > > kernel, or even in the systemd source, there are several places with |
33 |
> > > multiple copyright notices in them. |
34 |
> > |
35 |
> > Find me any project that organizes these into tables with years and |
36 |
> > copyright holders at the top of the file consistently as a matter of |
37 |
> > policy. As far as I can tell the Linux project has no consistent |
38 |
> > policy on this front, and systemd inherited numerous outside source |
39 |
> > trees as its scope expanded. |
40 |
> |
41 |
> We are not talking about demanding multiline headers for each |
42 |
> ebuild, we are talking about a policy allowing such headers if |
43 |
> necessary. This is the essentially same as Linux kernel does. |
44 |
|
45 |
The Linux kernel has no policy at all regarding copyright notices. |
46 |
So, they allow anything and everything as far as I can tell. Or, if |
47 |
they apply any filters it is just at the individual committer level as |
48 |
code trickles its way up. |
49 |
|
50 |
-- |
51 |
Rich |