1 |
On Wed, 14 Nov 2018 07:24:28 -0800 Rich Freeman wrote: |
2 |
> On Wed, Nov 14, 2018 at 6:45 AM Andrew Savchenko <bircoph@g.o> wrote: |
3 |
> > |
4 |
> > On Wed, 14 Nov 2018 07:50:48 -0800 Rich Freeman wrote: |
5 |
> > > On Tue, Nov 13, 2018 at 6:46 PM William Hubbs <williamh@g.o> wrote: |
6 |
> > > > |
7 |
> > > > On Tue, Nov 13, 2018 at 06:17:17PM -0800, Rich Freeman wrote: |
8 |
> > > > > On Tue, Nov 13, 2018 at 10:32 AM William Hubbs <williamh@g.o> wrote: |
9 |
> > > > > > |
10 |
> > > |
11 |
> > > Give me an example of a Linux kernel source file that contains a |
12 |
> > > multiline table of years and copyright holders. At best you'll find |
13 |
> > > random notices scattered around files in my experience, mostly because |
14 |
> > > of how the code was pulled in from outside. |
15 |
> > |
16 |
> > Sure, from line 4 to line 10: |
17 |
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/char/random.c |
18 |
> > |
19 |
> > Multiline table with copyright holders and separate years for each |
20 |
> > one. |
21 |
> |
22 |
> Sure, now look at the very next file in the same directory: |
23 |
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/char/raw.c |
24 |
> |
25 |
> No copyright notice at all. |
26 |
|
27 |
And there is nothing wrong with this. The point of my link was to |
28 |
prove that multiline copyright notices are used in well known |
29 |
projects. |
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 |
It doesn't matter if they have a written policy or not. It is |
51 |
matter that such headers are allowed. |
52 |
|
53 |
And please show me the FOSS project other than Gentoo or its |
54 |
derivatives which requires single line copyright header and |
55 |
explicitly forbids multiline copyright notices. |
56 |
|
57 |
|
58 |
Best regards, |
59 |
Andrew Savchenko |