* Re: Removing in-source contribution records contributer
2025-05-09 12:54 ` Alejandro Colomar
@ 2025-05-09 13:04 ` Stephen Kitt
2025-05-09 13:05 ` Mathieu Desnoyers
` (13 subsequent siblings)
14 siblings, 0 replies; 46+ messages in thread
From: Stephen Kitt @ 2025-05-09 13:04 UTC (permalink / raw)
To: Alejandro Colomar; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
Hi Alex,
On Fri, 9 May 2025 14:54:31 +0200, Alejandro Colomar <alx@kernel.org> wrote:
> I've added to BCC everyone whose copyright notices have been removed
> (those that noted an email). The full thread for this discussion can be
> found here:
> <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
>
> Please let me know if it's okay to you to transform your copyright
> notices to make them uniform? That is, do you approve
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> in what affects you?
That’s fine by me, I approve.
Regards,
Stephen
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 46+ messages in thread* Re: Removing in-source contribution records contributer
2025-05-09 12:54 ` Alejandro Colomar
2025-05-09 13:04 ` Stephen Kitt
@ 2025-05-09 13:05 ` Mathieu Desnoyers
2025-05-09 13:14 ` Carlos O'Donell
2025-05-09 13:39 ` Josef Bacik
` (12 subsequent siblings)
14 siblings, 1 reply; 46+ messages in thread
From: Mathieu Desnoyers @ 2025-05-09 13:05 UTC (permalink / raw)
To: Alejandro Colomar, linux-man; +Cc: Carlos O'Donell, G. Branden Robinson
On 2025-05-09 08:54, Alejandro Colomar wrote:
> Hi all,
>
> I've added to BCC everyone whose copyright notices have been removed
> (those that noted an email). The full thread for this discussion can be
> found here:
> <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
>
> Please let me know if it's okay to you to transform your copyright
> notices to make them uniform? That is, do you approve
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> in what affects you?
I was not sure if I should reply to all (including the mailing list).
Please clarify for others.
This change is OK as far as I am concerned. I'm always happy to
help lessen the maintenance burden. Eliminating redundant,
copyright information appears to be a good way to it.
The git history holds detailed information about the
line-by-line modifications to each file anyway.
Thanks,
Mathieu
>
> I've generated the BCC with
>
> $ git show 9f2986c34166085225bb5606ebfd4952054e1657 -- man \
> | grep '^-[^-]' \
> | grep @ \
> | grep -o '[^ ]*@[^ ]*' \
> | sed 's/,//g' \
> | sed 's/\.$//' \
> | sed 's/.*(//' \
> | sed 's/<//' \
> | sed 's/>//' \
> | sed 's/\.)//' \
> | sed 's/)//' \
> | sort \
> | uniq \
> | sed 's/^/Bcc: /';
>
>
> Have a lovely day!
> Alex
>
> On Tue, Apr 08, 2025 at 11:28:29PM +0200, Alejandro Colomar wrote:
>> Hi Carlos,
>>
>> On Tue, Apr 08, 2025 at 04:18:35PM -0400, Carlos O'Donell wrote:
>>> On 4/8/25 8:42 AM, G. Branden Robinson wrote:
>>>> Hi Alex,
>>>>
>>>> At 2025-04-08T01:05:02+0200, Alejandro Colomar wrote:
>>>>> On Thu, Feb 13, 2025 at 12:20:58AM +0100, Alejandro Colomar wrote:
>>>>>> On Wed, Feb 12, 2025 at 05:02:10PM -0600, G. Branden Robinson wrote:
>>>>>>> If you do this, I suggest you replace these lines with something
>>>>>>> like:
>>>>>>>
>>>>>>> .\" See the Git revision history at
>>>>>>> .\" $URL
>>>>>>> .\" for records of changes and contributors to this file.
>>>>>>
>>>>>> Good idea.
>>>>>
>>>>> I'm thinking I won't do that. I don't want to add that overhead to
>>>>> each page. People interested in the history of a page will already
>>>>> have a look at the git history, and there they'll find the old states
>>>>> of a page, in which they'll find this information.
>>>>>
>>>>> And it would require some non-trivial work to add this note
>>>>> consistently. I'll go with a removal without replacement, I think.
>>>>
>>>> Acknowledged. It's been a whole 7 weeks for so, so I don't clearly
>>>> remember my reasoning from February, but my suggestion may have been at
>>>> attempt to find a "conservative" alteration to file content or the
>>>> expressed meaning of the comments.
>>>>
>>>> But, what's conservative in one dimension often is not in another, such
>>>> as "labor required".
>>>>
>>>> I also agree that while Git is a complex suite of tools, "git log" is
>>>> not among its deeper magicks. At least not when run without arguments.
>>>
>>> We did something similar in glibc and created a CONTRIBUTED-BY file at the
>>> top-level and moved all contribution lines out of the respective
>>> files into the top-level file.
>>
>> Yep, a CREDITS file would be interesting. I wouldn't keep info about
>> which specific files were written by each contributor. That seems
>> something more appripriate for git-log(1). The pre-git contributions
>> will be visible in old versions of the pages (i.e., if one sees
>> Jane Random Developer in CREDITS and wonders which pages she contributed
>> to, they can `git log -S 'Jane Random Developer'` and similar commands
>> to find out.
>>
>> Thanks!
>>
>>
>> Have a lovely night!
>> Alex
>>
>>>
>>> e.g.
>>> ~~~
>>> The glibc project stopped adding "Contributed by" lines to source files in 2012
>>> in favour of acknowledging contributors in the glibc manual and through the git
>>> log. The record of existing "Contributed by" lines have now been moved to this
>>> file to acknowledge contributions by these developers to glibc.
>>>
>>> argp/argp-test.c:
>>> Written by Miles Bader <miles@gnu.ai.mit.edu>.
>>>
>>> argp/tst-argp1.c:
>>> Contributed by Ulrich Drepper <drepper@redhat.com>, 2002.
>>> ...
>>> ~~~
>>> The top-level CONTRIBUTED-BY has ~3,000 Contributed/Written by lines.
>>>
>>> Sme of the authors predated the use of git and so it was simpler to keep the
>>> lines somewhere as part of the transition away from "Contributed by"-style
>>> lines.
>>>
>>> --
>>> Cheers,
>>> Carlos.
>>>
>>>
>>
>> --
>> <https://www.alejandro-colomar.es/>
>
>
>
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
^ permalink raw reply [flat|nested] 46+ messages in thread* Re: Removing in-source contribution records contributer
2025-05-09 13:05 ` Mathieu Desnoyers
@ 2025-05-09 13:14 ` Carlos O'Donell
2025-05-09 13:31 ` Alejandro Colomar
0 siblings, 1 reply; 46+ messages in thread
From: Carlos O'Donell @ 2025-05-09 13:14 UTC (permalink / raw)
To: Mathieu Desnoyers, Alejandro Colomar, linux-man; +Cc: G. Branden Robinson
On 5/9/25 9:05 AM, Mathieu Desnoyers wrote:
> On 2025-05-09 08:54, Alejandro Colomar wrote:
>> Hi all,
>>
>> I've added to BCC everyone whose copyright notices have been removed
>> (those that noted an email). The full thread for this discussion can be
>> found here:
>> <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
>>
>> Please let me know if it's okay to you to transform your copyright
>> notices to make them uniform? That is, do you approve
>> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
>> in what affects you?
>
> I was not sure if I should reply to all (including the mailing list).
> Please clarify for others.
>
> This change is OK as far as I am concerned. I'm always happy to
> help lessen the maintenance burden. Eliminating redundant,
> copyright information appears to be a good way to it.
>
> The git history holds detailed information about the
> line-by-line modifications to each file anyway.
100% agree with Mathieu here.
This is OK for me and something we already did in glibc to lessen the
maintenance burden.
--
Cheers,
Carlos.
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 13:14 ` Carlos O'Donell
@ 2025-05-09 13:31 ` Alejandro Colomar
0 siblings, 0 replies; 46+ messages in thread
From: Alejandro Colomar @ 2025-05-09 13:31 UTC (permalink / raw)
To: Carlos O'Donell; +Cc: Mathieu Desnoyers, linux-man, G. Branden Robinson
[-- Attachment #1: Type: text/plain, Size: 1808 bytes --]
Hi Mathieu,
On Fri, May 09, 2025 at 09:14:56AM -0400, Carlos O'Donell wrote:
> On 5/9/25 9:05 AM, Mathieu Desnoyers wrote:
> > On 2025-05-09 08:54, Alejandro Colomar wrote:
> > > Hi all,
> > >
> > > I've added to BCC everyone whose copyright notices have been removed
> > > (those that noted an email). The full thread for this discussion can be
> > > found here:
> > > <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
> > >
> > > Please let me know if it's okay to you to transform your copyright
> > > notices to make them uniform? That is, do you approve
> > > <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> > > in what affects you?
> >
> > I was not sure if I should reply to all (including the mailing list).
> > Please clarify for others.
One person has replied in private, but all others in public. I prefer
if people reply in public, because then we have the list archives as a
record of the statement, which may have legal consequences.
I only used BCC, because having 100+ recipients is problematic.
Please reply on-list (but if someone prefers to reply off-list, that's
okay too).
> >
> > This change is OK as far as I am concerned. I'm always happy to
> > help lessen the maintenance burden. Eliminating redundant,
> > copyright information appears to be a good way to it.
> >
> > The git history holds detailed information about the
> > line-by-line modifications to each file anyway.
>
> 100% agree with Mathieu here.
>
> This is OK for me and something we already did in glibc to lessen the
> maintenance burden.
+1.
Thank you all!
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 12:54 ` Alejandro Colomar
2025-05-09 13:04 ` Stephen Kitt
2025-05-09 13:05 ` Mathieu Desnoyers
@ 2025-05-09 13:39 ` Josef Bacik
2025-05-09 13:50 ` наб
` (11 subsequent siblings)
14 siblings, 0 replies; 46+ messages in thread
From: Josef Bacik @ 2025-05-09 13:39 UTC (permalink / raw)
To: Alejandro Colomar; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
On Fri, May 9, 2025 at 8:55 AM Alejandro Colomar <alx@kernel.org> wrote:
>
> Hi all,
>
> I've added to BCC everyone whose copyright notices have been removed
> (those that noted an email). The full thread for this discussion can be
> found here:
> <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
>
> Please let me know if it's okay to you to transform your copyright
> notices to make them uniform? That is, do you approve
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> in what affects you?
My only concern is that we aren't lawyers (well at least I'm not), so
as long as we're following LF guidelines I'm fine with this. Thanks,
Josef
^ permalink raw reply [flat|nested] 46+ messages in thread* Re: Removing in-source contribution records contributer
2025-05-09 12:54 ` Alejandro Colomar
` (2 preceding siblings ...)
2025-05-09 13:39 ` Josef Bacik
@ 2025-05-09 13:50 ` наб
2025-05-09 13:55 ` Michael Haardt
` (10 subsequent siblings)
14 siblings, 0 replies; 46+ messages in thread
From: наб @ 2025-05-09 13:50 UTC (permalink / raw)
To: Alejandro Colomar; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
On Fri, May 09, 2025 at 02:54:31PM +0200, Alejandro Colomar wrote:
> Please let me know if it's okay to you to transform your copyright
> notices to make them uniform? That is, do you approve
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> in what affects you?
Yes
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 46+ messages in thread* Re: Removing in-source contribution records contributer
2025-05-09 12:54 ` Alejandro Colomar
` (3 preceding siblings ...)
2025-05-09 13:50 ` наб
@ 2025-05-09 13:55 ` Michael Haardt
2025-05-09 14:14 ` Dave Martin
` (9 subsequent siblings)
14 siblings, 0 replies; 46+ messages in thread
From: Michael Haardt @ 2025-05-09 13:55 UTC (permalink / raw)
To: Alejandro Colomar; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
Alejandro Colomar <alx@kernel.org> wrote:
> Please let me know if it's okay to you to transform your copyright
> notices to make them uniform? That is, do you approve
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> in what affects you?
Approved. Amazing how long ago that was.
Michael
^ permalink raw reply [flat|nested] 46+ messages in thread* Re: Removing in-source contribution records contributer
2025-05-09 12:54 ` Alejandro Colomar
` (4 preceding siblings ...)
2025-05-09 13:55 ` Michael Haardt
@ 2025-05-09 14:14 ` Dave Martin
2025-05-09 14:39 ` Alejandro Colomar
2025-05-09 14:16 ` Heinrich Schuchardt
` (8 subsequent siblings)
14 siblings, 1 reply; 46+ messages in thread
From: Dave Martin @ 2025-05-09 14:14 UTC (permalink / raw)
To: Alejandro Colomar; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
Hi,
On Fri, May 09, 2025 at 02:54:31PM +0200, Alejandro Colomar wrote:
> Hi all,
>
> I've added to BCC everyone whose copyright notices have been removed
> (those that noted an email). The full thread for this discussion can be
> found here:
> <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
>
> Please let me know if it's okay to you to transform your copyright
> notices to make them uniform? That is, do you approve
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> in what affects you?
Should the one-line replacement statement in each file refer back to
the CREDITS file?
Also, nothing seems to say that anyone listed in CREDITS actually
contributed copyrightable material to the project (as opposed to, say,
review effort, moral support or free pizza).
Renaming the CREDITS file to AUTHORS and/or clarifying this in a brief
top-level LICENSE / COPYING file might make the meaning clearer?
Either way, ack for the changes affecting me.
[...]
Cheers
---Dave
^ permalink raw reply [flat|nested] 46+ messages in thread* Re: Removing in-source contribution records contributer
2025-05-09 14:14 ` Dave Martin
@ 2025-05-09 14:39 ` Alejandro Colomar
2025-05-09 14:48 ` G. Branden Robinson
2025-05-09 15:43 ` Dave Martin
0 siblings, 2 replies; 46+ messages in thread
From: Alejandro Colomar @ 2025-05-09 14:39 UTC (permalink / raw)
To: Dave Martin; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
[-- Attachment #1: Type: text/plain, Size: 2374 bytes --]
Hi Dave,
On Fri, May 09, 2025 at 03:14:57PM +0100, Dave Martin wrote:
> Hi,
>
> On Fri, May 09, 2025 at 02:54:31PM +0200, Alejandro Colomar wrote:
> > Hi all,
> >
> > I've added to BCC everyone whose copyright notices have been removed
> > (those that noted an email). The full thread for this discussion can be
> > found here:
> > <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
> >
> > Please let me know if it's okay to you to transform your copyright
> > notices to make them uniform? That is, do you approve
> > <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> > in what affects you?
>
>
> Should the one-line replacement statement in each file refer back to
> the CREDITS file?
I prefer not, because then someone can copy the files to a different
repository, without needing to modify the notices (they might take the
CREDITS file as CREDITS_Linux-man-pages).
> Also, nothing seems to say that anyone listed in CREDITS actually
> contributed copyrightable material to the project (as opposed to, say,
> review effort, moral support or free pizza).
I initially planned to include reviewers, etc. into CREDITS. While
doing that, I realized that wasn't easy, because the file would be huge,
and would need to be updated too frequently; plus git(1) does a better
job of documenting that with the Reviewed-by, Cc, and other tags.
> Renaming the CREDITS file to AUTHORS and/or clarifying this in a brief
> top-level LICENSE / COPYING file might make the meaning clearer?
Yes, now that I discarded the idea of crediting *all* contributors, I
agree this file should be renamed to AUTHORS. Regarding a file solely
to clarify that the AUTHORS file holds the copyright holders of the
project, I guess by calling it AUTHORS it would already be obvious. I'm
hesitant to add another file for explaining that because the more
uppercase files there are in the root of the repo, the harder it is to
understand their relationship. However, I can add something in the
README, where I already document what each file is.
> Either way, ack for the changes affecting me.
Thanks!
Have a lovely day!
Alex
>
> [...]
>
> Cheers
> ---Dave
>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 14:39 ` Alejandro Colomar
@ 2025-05-09 14:48 ` G. Branden Robinson
2025-05-09 15:43 ` Dave Martin
1 sibling, 0 replies; 46+ messages in thread
From: G. Branden Robinson @ 2025-05-09 14:48 UTC (permalink / raw)
To: linux-man; +Cc: groff
[-- Attachment #1: Type: text/plain, Size: 3645 bytes --]
[CCing groff list because I bring up some project management details]
Hi Dave & Alex,
At 2025-05-09T15:14:57+0100, Dave Martin wrote:
> Should the one-line replacement statement in each file refer back to
> the CREDITS file?
>
> Also, nothing seems to say that anyone listed in CREDITS actually
> contributed copyrightable material to the project (as opposed to, say,
> review effort, moral support or free pizza).
>
> Renaming the CREDITS file to AUTHORS and/or clarifying this in a brief
> top-level LICENSE / COPYING file might make the meaning clearer?
At 2025-05-09T16:39:05+0200, Alejandro Colomar wrote:
> I prefer not, because then someone can copy the files to a different
> repository, without needing to modify the notices (they might take the
> CREDITS file as CREDITS_Linux-man-pages).
>
> > Also, nothing seems to say that anyone listed in CREDITS actually
> > contributed copyrightable material to the project (as opposed to, say,
> > review effort, moral support or free pizza).
>
> I initially planned to include reviewers, etc. into CREDITS. While
> doing that, I realized that wasn't easy, because the file would be
> huge, and would need to be updated too frequently; plus git(1) does a
> better job of documenting that with the Reviewed-by, Cc, and other
> tags.
>
> > Renaming the CREDITS file to AUTHORS and/or clarifying this in a
> > brief top-level LICENSE / COPYING file might make the meaning
> > clearer?
>
> Yes, now that I discarded the idea of crediting *all* contributors, I
> agree this file should be renamed to AUTHORS. Regarding a file solely
> to clarify that the AUTHORS file holds the copyright holders of the
> project, I guess by calling it AUTHORS it would already be obvious.
> I'm hesitant to add another file for explaining that because the more
> uppercase files there are in the root of the repo, the harder it is to
> understand their relationship. However, I can add something in the
> README, where I already document what each file is.
Yes, this is consistent with GNU approach--as I understand it--of having
an "AUTHORS" file for copyright holders and a "THANKS" file for
acknowledgement of anyone who isn't a copyright holder.
Before anyone asks, groff doesn't use that approach, I think because it
is so old (starting 1989) and predates some GNU common practices.
On my get-around-to-it list is to determine who's actually signed
copyright assignment paperwork to the FSF for their groff contributions,
and who has not. Anyone who had made a significant enough contribution
that copyright assignment would be worth the trouble would be listed in
AUTHORS whether they'd executed the assignment paperwork or not.
Also, since the contrary is a common misconception, the FSF does not
_require_ copyright assignment.
'GNU packages need not be FSF-copyrighted; this is up to the author(s),
generally at the time the package is dubbed GNU. When copyright is
assigned to the FSF, the FSF has authority to act to stop GPL violations
about the package (otherwise, legal actions are up to the author(s)). It
also allows us to grant additional permissions on a package, such as an
exception, if the need should arise. Additionally, holding the copyright
allows us to upgrade the license of a package even if it had been
initially released under "GPLv2 only" (instead of the "or later"
licensing option as recommended by the FSF). The rest of this section is
about the case when a package is FSF-copyrighted.'
https://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html#Copyright-Papers
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 14:39 ` Alejandro Colomar
2025-05-09 14:48 ` G. Branden Robinson
@ 2025-05-09 15:43 ` Dave Martin
2025-05-09 18:49 ` Alejandro Colomar
1 sibling, 1 reply; 46+ messages in thread
From: Dave Martin @ 2025-05-09 15:43 UTC (permalink / raw)
To: Alejandro Colomar; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
Hi,
On Fri, May 09, 2025 at 04:39:05PM +0200, Alejandro Colomar wrote:
> Hi Dave,
>
> On Fri, May 09, 2025 at 03:14:57PM +0100, Dave Martin wrote:
> > Hi,
> >
> > On Fri, May 09, 2025 at 02:54:31PM +0200, Alejandro Colomar wrote:
> > > Hi all,
> > >
> > > I've added to BCC everyone whose copyright notices have been removed
> > > (those that noted an email). The full thread for this discussion can be
> > > found here:
> > > <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
> > >
> > > Please let me know if it's okay to you to transform your copyright
> > > notices to make them uniform? That is, do you approve
> > > <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> > > in what affects you?
> >
> >
> > Should the one-line replacement statement in each file refer back to
> > the CREDITS file?
>
> I prefer not, because then someone can copy the files to a different
> repository, without needing to modify the notices (they might take the
> CREDITS file as CREDITS_Linux-man-pages).
Fair enough, though would it make sense for the boilerplate line to at
least become
# Copyright, The authors of the Linux man-pages project
...?
This remains meaningful out of context, but when shipped with the
original tree this wording macthes up with the naming of the AUTHORS
file (assuming that's what the file is called).
> > Also, nothing seems to say that anyone listed in CREDITS actually
> > contributed copyrightable material to the project (as opposed to, say,
> > review effort, moral support or free pizza).
>
> I initially planned to include reviewers, etc. into CREDITS. While
> doing that, I realized that wasn't easy, because the file would be huge,
> and would need to be updated too frequently; plus git(1) does a better
> job of documenting that with the Reviewed-by, Cc, and other tags.
Fair enough. A line has to be drawn somewhere.
> > Renaming the CREDITS file to AUTHORS and/or clarifying this in a brief
> > top-level LICENSE / COPYING file might make the meaning clearer?
>
> Yes, now that I discarded the idea of crediting *all* contributors, I
> agree this file should be renamed to AUTHORS. Regarding a file solely
> to clarify that the AUTHORS file holds the copyright holders of the
> project, I guess by calling it AUTHORS it would already be obvious. I'm
> hesitant to add another file for explaining that because the more
> uppercase files there are in the root of the repo, the harder it is to
> understand their relationship. However, I can add something in the
> README, where I already document what each file is.
Ack, it's probably fairly obvious what a file called "AUTHORS" means.
Just a suggestion, would something like this work in README:
+ AUTHORS
+ List of individuals and organizations that have contributed
+ content to the project.
+
This will still be a true description regardless of whether the list
is complete or if non page content contributors are included. (There
are probably plenty of borderline cases as to whether something counts
as a page content contribution or not.)
Cheers
---Dave
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 15:43 ` Dave Martin
@ 2025-05-09 18:49 ` Alejandro Colomar
2025-05-09 19:07 ` Alejandro Colomar
0 siblings, 1 reply; 46+ messages in thread
From: Alejandro Colomar @ 2025-05-09 18:49 UTC (permalink / raw)
To: Dave Martin; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
[-- Attachment #1: Type: text/plain, Size: 3170 bytes --]
Hi Dave,
On Fri, May 09, 2025 at 04:43:36PM +0100, Dave Martin wrote:
> > > Should the one-line replacement statement in each file refer back to
> > > the CREDITS file?
> >
> > I prefer not, because then someone can copy the files to a different
> > repository, without needing to modify the notices (they might take the
> > CREDITS file as CREDITS_Linux-man-pages).
>
> Fair enough, though would it make sense for the boilerplate line to at
> least become
>
> # Copyright, The authors of the Linux man-pages project
>
> ...?
>
> This remains meaningful out of context, but when shipped with the
> original tree this wording macthes up with the naming of the AUTHORS
> file (assuming that's what the file is called).
Hmmmm. I see the point. That sounds very reasonable. Contributors
sounded more like inclusive of anyone who passes by and writes a few
lines, as opposed to authors which are usually considered only the long-
term ones. But since we would list all of them as AUTHORS, they're
clearly included. So, I'm going to do that change.
> > > Renaming the CREDITS file to AUTHORS and/or clarifying this in a brief
> > > top-level LICENSE / COPYING file might make the meaning clearer?
> >
> > Yes, now that I discarded the idea of crediting *all* contributors, I
> > agree this file should be renamed to AUTHORS. Regarding a file solely
> > to clarify that the AUTHORS file holds the copyright holders of the
> > project, I guess by calling it AUTHORS it would already be obvious. I'm
> > hesitant to add another file for explaining that because the more
> > uppercase files there are in the root of the repo, the harder it is to
> > understand their relationship. However, I can add something in the
> > README, where I already document what each file is.
>
> Ack, it's probably fairly obvious what a file called "AUTHORS" means.
>
> Just a suggestion, would something like this work in README:
>
> + AUTHORS
> + List of individuals and organizations that have contributed
> + content to the project.
> +
Certainly. Thanks!
> This will still be a true description regardless of whether the list
> is complete or if non page content contributors are included. (There
> are probably plenty of borderline cases as to whether something counts
> as a page content contribution or not.)
Yep. For now, I haven't documented it, but I've drawn the line at:
- Had its name either in a copyright notice,
- or in a source line saying something like "modified by"
- or was 'Author' in a git commit.
Anyone who meets at least one of those has been included in CREDITS (to
be renamed to AUTHORS).
Exceptions are authors of code that was taken by this project, but who
didn't contribute to this project themselves. For example, the regents
of the University of California wrote pages that have been incorporated
into this project, but they didn't consciously contribute to this
project. Thus, I've retained their copyright notices, and didn't add
them to CREDITS.
Cheers,
Alex
>
> Cheers
> ---Dave
>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 18:49 ` Alejandro Colomar
@ 2025-05-09 19:07 ` Alejandro Colomar
2025-05-12 11:40 ` Dave Martin
0 siblings, 1 reply; 46+ messages in thread
From: Alejandro Colomar @ 2025-05-09 19:07 UTC (permalink / raw)
To: Dave Martin; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
[-- Attachment #1: Type: text/plain, Size: 3820 bytes --]
Hi Dave,
On Fri, May 09, 2025 at 08:49:39PM +0200, Alejandro Colomar wrote:
> Hi Dave,
>
> On Fri, May 09, 2025 at 04:43:36PM +0100, Dave Martin wrote:
> > > > Should the one-line replacement statement in each file refer back to
> > > > the CREDITS file?
> > >
> > > I prefer not, because then someone can copy the files to a different
> > > repository, without needing to modify the notices (they might take the
> > > CREDITS file as CREDITS_Linux-man-pages).
> >
> > Fair enough, though would it make sense for the boilerplate line to at
> > least become
> >
> > # Copyright, The authors of the Linux man-pages project
> >
> > ...?
> >
> > This remains meaningful out of context, but when shipped with the
> > original tree this wording macthes up with the naming of the AUTHORS
> > file (assuming that's what the file is called).
>
> Hmmmm. I see the point. That sounds very reasonable. Contributors
> sounded more like inclusive of anyone who passes by and writes a few
> lines, as opposed to authors which are usually considered only the long-
> term ones. But since we would list all of them as AUTHORS, they're
> clearly included. So, I'm going to do that change.
>
> > > > Renaming the CREDITS file to AUTHORS and/or clarifying this in a brief
> > > > top-level LICENSE / COPYING file might make the meaning clearer?
> > >
> > > Yes, now that I discarded the idea of crediting *all* contributors, I
> > > agree this file should be renamed to AUTHORS. Regarding a file solely
> > > to clarify that the AUTHORS file holds the copyright holders of the
> > > project, I guess by calling it AUTHORS it would already be obvious. I'm
> > > hesitant to add another file for explaining that because the more
> > > uppercase files there are in the root of the repo, the harder it is to
> > > understand their relationship. However, I can add something in the
> > > README, where I already document what each file is.
> >
> > Ack, it's probably fairly obvious what a file called "AUTHORS" means.
> >
> > Just a suggestion, would something like this work in README:
> >
> > + AUTHORS
> > + List of individuals and organizations that have contributed
> > + content to the project.
> > +
>
> Certainly. Thanks!
>
> > This will still be a true description regardless of whether the list
> > is complete or if non page content contributors are included. (There
> > are probably plenty of borderline cases as to whether something counts
> > as a page content contribution or not.)
>
> Yep. For now, I haven't documented it, but I've drawn the line at:
>
> - Had its name either in a copyright notice,
> - or in a source line saying something like "modified by"
> - or was 'Author' in a git commit.
>
> Anyone who meets at least one of those has been included in CREDITS (to
> be renamed to AUTHORS).
>
> Exceptions are authors of code that was taken by this project, but who
> didn't contribute to this project themselves. For example, the regents
> of the University of California wrote pages that have been incorporated
> into this project, but they didn't consciously contribute to this
> project. Thus, I've retained their copyright notices, and didn't add
> them to CREDITS.
I've applied both changes already (currently in my branch):
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=98c87fcf783f20da7aae8adbe21e1954d9e8f310>
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=d5218b220e41a1ed031eea6219237fda0a93d9b2>
Cheers,
Alex
>
>
> Cheers,
> Alex
>
> >
> > Cheers
> > ---Dave
> >
>
> --
> <https://www.alejandro-colomar.es/>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 19:07 ` Alejandro Colomar
@ 2025-05-12 11:40 ` Dave Martin
0 siblings, 0 replies; 46+ messages in thread
From: Dave Martin @ 2025-05-12 11:40 UTC (permalink / raw)
To: Alejandro Colomar; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
Hi,
On Fri, May 09, 2025 at 09:07:47PM +0200, Alejandro Colomar wrote:
> Hi Dave,
>
> On Fri, May 09, 2025 at 08:49:39PM +0200, Alejandro Colomar wrote:
> > Hi Dave,
> >
> > On Fri, May 09, 2025 at 04:43:36PM +0100, Dave Martin wrote:
[...]
> > > Just a suggestion, would something like this work in README:
> > >
> > > + AUTHORS
> > > + List of individuals and organizations that have contributed
> > > + content to the project.
> > > +
> >
> > Certainly. Thanks!
> >
> > > This will still be a true description regardless of whether the list
> > > is complete or if non page content contributors are included. (There
> > > are probably plenty of borderline cases as to whether something counts
> > > as a page content contribution or not.)
> >
> > Yep. For now, I haven't documented it, but I've drawn the line at:
> >
> > - Had its name either in a copyright notice,
> > - or in a source line saying something like "modified by"
> > - or was 'Author' in a git commit.
> >
> > Anyone who meets at least one of those has been included in CREDITS (to
> > be renamed to AUTHORS).
> >
> > Exceptions are authors of code that was taken by this project, but who
> > didn't contribute to this project themselves. For example, the regents
> > of the University of California wrote pages that have been incorporated
> > into this project, but they didn't consciously contribute to this
> > project. Thus, I've retained their copyright notices, and didn't add
> > them to CREDITS.
Seems reasonable.
> I've applied both changes already (currently in my branch):
>
> <https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=98c87fcf783f20da7aae8adbe21e1954d9e8f310>
> <https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=d5218b220e41a1ed031eea6219237fda0a93d9b2>
Looks good to me. Thanks for the credit.
Cheers
---Dave
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 12:54 ` Alejandro Colomar
` (5 preceding siblings ...)
2025-05-09 14:14 ` Dave Martin
@ 2025-05-09 14:16 ` Heinrich Schuchardt
2025-05-09 15:13 ` Tycho Andersen
` (7 subsequent siblings)
14 siblings, 0 replies; 46+ messages in thread
From: Heinrich Schuchardt @ 2025-05-09 14:16 UTC (permalink / raw)
To: Alejandro Colomar, linux-man; +Cc: Carlos O'Donell, G. Branden Robinson
Am 9. Mai 2025 14:54:31 MESZ schrieb Alejandro Colomar <alx@kernel.org>:
>Hi all,
>
>I've added to BCC everyone whose copyright notices have been removed
>(those that noted an email). The full thread for this discussion can be
>found here:
><https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
>
>Please let me know if it's okay to you to transform your copyright
>notices to make them uniform? That is, do you approve
><https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
>in what affects you?
Fine for me.
Best regards
Heinrich
>
>I've generated the BCC with
>
> $ git show 9f2986c34166085225bb5606ebfd4952054e1657 -- man \
> | grep '^-[^-]' \
> | grep @ \
> | grep -o '[^ ]*@[^ ]*' \
> | sed 's/,//g' \
> | sed 's/\.$//' \
> | sed 's/.*(//' \
> | sed 's/<//' \
> | sed 's/>//' \
> | sed 's/\.)//' \
> | sed 's/)//' \
> | sort \
> | uniq \
> | sed 's/^/Bcc: /';
>
>
>Have a lovely day!
>Alex
>
>On Tue, Apr 08, 2025 at 11:28:29PM +0200, Alejandro Colomar wrote:
>> Hi Carlos,
>>
>> On Tue, Apr 08, 2025 at 04:18:35PM -0400, Carlos O'Donell wrote:
>> > On 4/8/25 8:42 AM, G. Branden Robinson wrote:
>> > > Hi Alex,
>> > >
>> > > At 2025-04-08T01:05:02+0200, Alejandro Colomar wrote:
>> > > > On Thu, Feb 13, 2025 at 12:20:58AM +0100, Alejandro Colomar wrote:
>> > > > > On Wed, Feb 12, 2025 at 05:02:10PM -0600, G. Branden Robinson wrote:
>> > > > > > If you do this, I suggest you replace these lines with something
>> > > > > > like:
>> > > > > >
>> > > > > > .\" See the Git revision history at
>> > > > > > .\" $URL
>> > > > > > .\" for records of changes and contributors to this file.
>> > > > >
>> > > > > Good idea.
>> > > >
>> > > > I'm thinking I won't do that. I don't want to add that overhead to
>> > > > each page. People interested in the history of a page will already
>> > > > have a look at the git history, and there they'll find the old states
>> > > > of a page, in which they'll find this information.
>> > > >
>> > > > And it would require some non-trivial work to add this note
>> > > > consistently. I'll go with a removal without replacement, I think.
>> > >
>> > > Acknowledged. It's been a whole 7 weeks for so, so I don't clearly
>> > > remember my reasoning from February, but my suggestion may have been at
>> > > attempt to find a "conservative" alteration to file content or the
>> > > expressed meaning of the comments.
>> > >
>> > > But, what's conservative in one dimension often is not in another, such
>> > > as "labor required".
>> > >
>> > > I also agree that while Git is a complex suite of tools, "git log" is
>> > > not among its deeper magicks. At least not when run without arguments.
>> >
>> > We did something similar in glibc and created a CONTRIBUTED-BY file at the
>> > top-level and moved all contribution lines out of the respective
>> > files into the top-level file.
>>
>> Yep, a CREDITS file would be interesting. I wouldn't keep info about
>> which specific files were written by each contributor. That seems
>> something more appripriate for git-log(1). The pre-git contributions
>> will be visible in old versions of the pages (i.e., if one sees
>> Jane Random Developer in CREDITS and wonders which pages she contributed
>> to, they can `git log -S 'Jane Random Developer'` and similar commands
>> to find out.
>>
>> Thanks!
>>
>>
>> Have a lovely night!
>> Alex
>>
>> >
>> > e.g.
>> > ~~~
>> > The glibc project stopped adding "Contributed by" lines to source files in 2012
>> > in favour of acknowledging contributors in the glibc manual and through the git
>> > log. The record of existing "Contributed by" lines have now been moved to this
>> > file to acknowledge contributions by these developers to glibc.
>> >
>> > argp/argp-test.c:
>> > Written by Miles Bader <miles@gnu.ai.mit.edu>.
>> >
>> > argp/tst-argp1.c:
>> > Contributed by Ulrich Drepper <drepper@redhat.com>, 2002.
>> > ...
>> > ~~~
>> > The top-level CONTRIBUTED-BY has ~3,000 Contributed/Written by lines.
>> >
>> > Sme of the authors predated the use of git and so it was simpler to keep the
>> > lines somewhere as part of the transition away from "Contributed by"-style
>> > lines.
>> >
>> > --
>> > Cheers,
>> > Carlos.
>> >
>> >
>>
>> --
>> <https://www.alejandro-colomar.es/>
>
>
>
^ permalink raw reply [flat|nested] 46+ messages in thread* Re: Removing in-source contribution records contributer
2025-05-09 12:54 ` Alejandro Colomar
` (6 preceding siblings ...)
2025-05-09 14:16 ` Heinrich Schuchardt
@ 2025-05-09 15:13 ` Tycho Andersen
2025-05-09 18:35 ` Alejandro Colomar
2025-05-09 18:22 ` Christoph Lameter (Ampere)
` (6 subsequent siblings)
14 siblings, 1 reply; 46+ messages in thread
From: Tycho Andersen @ 2025-05-09 15:13 UTC (permalink / raw)
To: Alejandro Colomar; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
Hi Alex,
On Fri, May 09, 2025 at 02:54:31PM +0200, Alejandro Colomar wrote:
> Hi all,
>
> I've added to BCC everyone whose copyright notices have been removed
> (those that noted an email). The full thread for this discussion can be
> found here:
> <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
>
> Please let me know if it's okay to you to transform your copyright
> notices to make them uniform? That is, do you approve
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> in what affects you?
(thanks for clarifying about posting on-list.)
Yes, I approve. (Though I have changed to using tycho@tycho.pizza as
my primary e-mail address, it would be handy if you could make that
correction during this process as well, but not required.)
Cheers,
Tycho
^ permalink raw reply [flat|nested] 46+ messages in thread* Re: Removing in-source contribution records contributer
2025-05-09 15:13 ` Tycho Andersen
@ 2025-05-09 18:35 ` Alejandro Colomar
2025-05-09 20:56 ` Tycho Andersen
0 siblings, 1 reply; 46+ messages in thread
From: Alejandro Colomar @ 2025-05-09 18:35 UTC (permalink / raw)
To: Tycho Andersen; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
On Fri, May 09, 2025 at 09:13:23AM -0600, Tycho Andersen wrote:
> Hi Alex,
Hi Tycho,
>
> On Fri, May 09, 2025 at 02:54:31PM +0200, Alejandro Colomar wrote:
> > Hi all,
> >
> > I've added to BCC everyone whose copyright notices have been removed
> > (those that noted an email). The full thread for this discussion can be
> > found here:
> > <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
> >
> > Please let me know if it's okay to you to transform your copyright
> > notices to make them uniform? That is, do you approve
> > <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> > in what affects you?
>
> (thanks for clarifying about posting on-list.)
>
> Yes, I approve. (Though I have changed to using tycho@tycho.pizza as
> my primary e-mail address, it would be handy if you could make that
> correction during this process as well, but not required.)
Thanks! (I had already added you to CREDITS with that address, unless
I'm mistaken. Can you please check if all's good?)
Have a lovely day!
Alex
>
> Cheers,
>
> Tycho
>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 18:35 ` Alejandro Colomar
@ 2025-05-09 20:56 ` Tycho Andersen
2025-05-09 21:11 ` Alejandro Colomar
0 siblings, 1 reply; 46+ messages in thread
From: Tycho Andersen @ 2025-05-09 20:56 UTC (permalink / raw)
To: Alejandro Colomar; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
On Fri, May 09, 2025 at 08:35:15PM +0200, Alejandro Colomar wrote:
> On Fri, May 09, 2025 at 09:13:23AM -0600, Tycho Andersen wrote:
> > Hi Alex,
>
> Hi Tycho,
>
> >
> > On Fri, May 09, 2025 at 02:54:31PM +0200, Alejandro Colomar wrote:
> > > Hi all,
> > >
> > > I've added to BCC everyone whose copyright notices have been removed
> > > (those that noted an email). The full thread for this discussion can be
> > > found here:
> > > <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
> > >
> > > Please let me know if it's okay to you to transform your copyright
> > > notices to make them uniform? That is, do you approve
> > > <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> > > in what affects you?
> >
> > (thanks for clarifying about posting on-list.)
> >
> > Yes, I approve. (Though I have changed to using tycho@tycho.pizza as
> > my primary e-mail address, it would be handy if you could make that
> > correction during this process as well, but not required.)
>
> Thanks! (I had already added you to CREDITS with that address, unless
> I'm mistaken. Can you please check if all's good?)
Here I see:
https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/diff/CREDITS?id=9f2986c34166085225bb5606ebfd4952054e1657
tycho@tycho.ws; but it's also fine if you want to keep the commit id
the same.
Cheers,
Tycho
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 20:56 ` Tycho Andersen
@ 2025-05-09 21:11 ` Alejandro Colomar
2025-05-10 22:24 ` Tycho Andersen
0 siblings, 1 reply; 46+ messages in thread
From: Alejandro Colomar @ 2025-05-09 21:11 UTC (permalink / raw)
To: Tycho Andersen; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]
Hi Tycho,
On Fri, May 09, 2025 at 02:56:01PM -0600, Tycho Andersen wrote:
> > > Yes, I approve. (Though I have changed to using tycho@tycho.pizza as
> > > my primary e-mail address, it would be handy if you could make that
> > > correction during this process as well, but not required.)
> >
> > Thanks! (I had already added you to CREDITS with that address, unless
> > I'm mistaken. Can you please check if all's good?)
>
> Here I see:
>
> https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/diff/CREDITS?id=9f2986c34166085225bb5606ebfd4952054e1657
>
> tycho@tycho.ws; but it's also fine if you want to keep the commit id
> the same.
Ahh, I see. There are three commits that touch that file: The first
one took the names from "modified by" and similar lines in source code.
(You don't appear in that one.) The second one took the names from
copyright notices. I picked @tycho.ws in that one. Then, the third one
took names from commit Author. In that one, I updated your main to the
@tycho.pizza one.
$ git log -p man-pages-6.14 -- AUTHORS CREDITS \
| grep \
-e ^commit \
-e ^Date: \
-e '^ \(CREDITS\|AUTHORS\|\*\|man/\)' \
-e tycho \
-e ^--- -e ^+++
commit 0cf255ac79231999d79cd656f81013089d2d4153
Date: Fri Apr 11 16:15:50 2025 +0200
CREDITS: Add commit authors
--- a/CREDITS
+++ b/CREDITS
-Tycho Andersen <tycho@tycho.ws>
+Tycho Andersen <tycho@tycho.pizza>
commit 9f2986c34166085225bb5606ebfd4952054e1657
Date: Fri Apr 11 02:19:48 2025 +0200
*, CREDITS: Unify copyright notices
--- a/CREDITS
+++ b/CREDITS
+Tycho Andersen <tycho@tycho.ws>
commit 52b7bab3a44fb5d2d464fa8acd6beee3b62269aa
Date: Fri Mar 14 14:02:41 2025 +0100
man/, CREDITS: Move in-source contribution records to CREDITS
--- /dev/null
+++ b/CREDITS
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 21:11 ` Alejandro Colomar
@ 2025-05-10 22:24 ` Tycho Andersen
0 siblings, 0 replies; 46+ messages in thread
From: Tycho Andersen @ 2025-05-10 22:24 UTC (permalink / raw)
To: Alejandro Colomar; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
On Fri, May 09, 2025 at 11:11:08PM +0200, Alejandro Colomar wrote:
> Hi Tycho,
>
> On Fri, May 09, 2025 at 02:56:01PM -0600, Tycho Andersen wrote:
> > > > Yes, I approve. (Though I have changed to using tycho@tycho.pizza as
> > > > my primary e-mail address, it would be handy if you could make that
> > > > correction during this process as well, but not required.)
> > >
> > > Thanks! (I had already added you to CREDITS with that address, unless
> > > I'm mistaken. Can you please check if all's good?)
> >
> > Here I see:
> >
> > https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/diff/CREDITS?id=9f2986c34166085225bb5606ebfd4952054e1657
> >
> > tycho@tycho.ws; but it's also fine if you want to keep the commit id
> > the same.
>
> Ahh, I see. There are three commits that touch that file: The first
> one took the names from "modified by" and similar lines in source code.
> (You don't appear in that one.) The second one took the names from
> copyright notices. I picked @tycho.ws in that one. Then, the third one
> took names from commit Author. In that one, I updated your main to the
> @tycho.pizza one.
>
> $ git log -p man-pages-6.14 -- AUTHORS CREDITS \
> | grep \
> -e ^commit \
> -e ^Date: \
> -e '^ \(CREDITS\|AUTHORS\|\*\|man/\)' \
> -e tycho \
> -e ^--- -e ^+++
> commit 0cf255ac79231999d79cd656f81013089d2d4153
> Date: Fri Apr 11 16:15:50 2025 +0200
> CREDITS: Add commit authors
> --- a/CREDITS
> +++ b/CREDITS
> -Tycho Andersen <tycho@tycho.ws>
> +Tycho Andersen <tycho@tycho.pizza>
> commit 9f2986c34166085225bb5606ebfd4952054e1657
> Date: Fri Apr 11 02:19:48 2025 +0200
> *, CREDITS: Unify copyright notices
> --- a/CREDITS
> +++ b/CREDITS
> +Tycho Andersen <tycho@tycho.ws>
> commit 52b7bab3a44fb5d2d464fa8acd6beee3b62269aa
> Date: Fri Mar 14 14:02:41 2025 +0100
> man/, CREDITS: Move in-source contribution records to CREDITS
> --- /dev/null
> +++ b/CREDITS
Looks great, thank you.
Tycho
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 12:54 ` Alejandro Colomar
` (7 preceding siblings ...)
2025-05-09 15:13 ` Tycho Andersen
@ 2025-05-09 18:22 ` Christoph Lameter (Ampere)
2025-05-09 18:53 ` Alejandro Colomar
2025-05-09 18:31 ` Christoph Lameter (Ampere)
` (5 subsequent siblings)
14 siblings, 1 reply; 46+ messages in thread
From: Christoph Lameter (Ampere) @ 2025-05-09 18:22 UTC (permalink / raw)
To: Alejandro Colomar; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
There is a pending patch to standardize all my email addresses in the
kernel. This patch may conflict with the one in Andrew's tree.
The Email address going forward should be
Christoph Lameter <cl@gentwo.org>
On Fri, 9 May 2025, Alejandro Colomar wrote:
> Hi all,
>
> I've added to BCC everyone whose copyright notices have been removed
> (those that noted an email). The full thread for this discussion can be
> found here:
> <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
>
> Please let me know if it's okay to you to transform your copyright
> notices to make them uniform? That is, do you approve
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> in what affects you?
>
> I've generated the BCC with
>
> $ git show 9f2986c34166085225bb5606ebfd4952054e1657 -- man \
> | grep '^-[^-]' \
> | grep @ \
> | grep -o '[^ ]*@[^ ]*' \
> | sed 's/,//g' \
> | sed 's/\.$//' \
> | sed 's/.*(//' \
> | sed 's/<//' \
> | sed 's/>//' \
> | sed 's/\.)//' \
> | sed 's/)//' \
> | sort \
> | uniq \
> | sed 's/^/Bcc: /';
>
>
> Have a lovely day!
> Alex
>
> On Tue, Apr 08, 2025 at 11:28:29PM +0200, Alejandro Colomar wrote:
> > Hi Carlos,
> >
> > On Tue, Apr 08, 2025 at 04:18:35PM -0400, Carlos O'Donell wrote:
> > > On 4/8/25 8:42 AM, G. Branden Robinson wrote:
> > > > Hi Alex,
> > > >
> > > > At 2025-04-08T01:05:02+0200, Alejandro Colomar wrote:
> > > > > On Thu, Feb 13, 2025 at 12:20:58AM +0100, Alejandro Colomar wrote:
> > > > > > On Wed, Feb 12, 2025 at 05:02:10PM -0600, G. Branden Robinson wrote:
> > > > > > > If you do this, I suggest you replace these lines with something
> > > > > > > like:
> > > > > > >
> > > > > > > .\" See the Git revision history at
> > > > > > > .\" $URL
> > > > > > > .\" for records of changes and contributors to this file.
> > > > > >
> > > > > > Good idea.
> > > > >
> > > > > I'm thinking I won't do that. I don't want to add that overhead to
> > > > > each page. People interested in the history of a page will already
> > > > > have a look at the git history, and there they'll find the old states
> > > > > of a page, in which they'll find this information.
> > > > >
> > > > > And it would require some non-trivial work to add this note
> > > > > consistently. I'll go with a removal without replacement, I think.
> > > >
> > > > Acknowledged. It's been a whole 7 weeks for so, so I don't clearly
> > > > remember my reasoning from February, but my suggestion may have been at
> > > > attempt to find a "conservative" alteration to file content or the
> > > > expressed meaning of the comments.
> > > >
> > > > But, what's conservative in one dimension often is not in another, such
> > > > as "labor required".
> > > >
> > > > I also agree that while Git is a complex suite of tools, "git log" is
> > > > not among its deeper magicks. At least not when run without arguments.
> > >
> > > We did something similar in glibc and created a CONTRIBUTED-BY file at the
> > > top-level and moved all contribution lines out of the respective
> > > files into the top-level file.
> >
> > Yep, a CREDITS file would be interesting. I wouldn't keep info about
> > which specific files were written by each contributor. That seems
> > something more appripriate for git-log(1). The pre-git contributions
> > will be visible in old versions of the pages (i.e., if one sees
> > Jane Random Developer in CREDITS and wonders which pages she contributed
> > to, they can `git log -S 'Jane Random Developer'` and similar commands
> > to find out.
> >
> > Thanks!
> >
> >
> > Have a lovely night!
> > Alex
> >
> > >
> > > e.g.
> > > ~~~
> > > The glibc project stopped adding "Contributed by" lines to source files in 2012
> > > in favour of acknowledging contributors in the glibc manual and through the git
> > > log. The record of existing "Contributed by" lines have now been moved to this
> > > file to acknowledge contributions by these developers to glibc.
> > >
> > > argp/argp-test.c:
> > > Written by Miles Bader <miles@gnu.ai.mit.edu>.
> > >
> > > argp/tst-argp1.c:
> > > Contributed by Ulrich Drepper <drepper@redhat.com>, 2002.
> > > ...
> > > ~~~
> > > The top-level CONTRIBUTED-BY has ~3,000 Contributed/Written by lines.
> > >
> > > Sme of the authors predated the use of git and so it was simpler to keep the
> > > lines somewhere as part of the transition away from "Contributed by"-style
> > > lines.
> > >
> > > --
> > > Cheers,
> > > Carlos.
> > >
> > >
> >
> > --
> > <https://www.alejandro-colomar.es/>
>
>
>
>
^ permalink raw reply [flat|nested] 46+ messages in thread* Re: Removing in-source contribution records contributer
2025-05-09 18:22 ` Christoph Lameter (Ampere)
@ 2025-05-09 18:53 ` Alejandro Colomar
0 siblings, 0 replies; 46+ messages in thread
From: Alejandro Colomar @ 2025-05-09 18:53 UTC (permalink / raw)
To: Christoph Lameter (Ampere)
Cc: linux-man, Carlos O'Donell, G. Branden Robinson
[-- Attachment #1: Type: text/plain, Size: 5308 bytes --]
Hi Christoph,
On Fri, May 09, 2025 at 11:22:21AM -0700, Christoph Lameter (Ampere) wrote:
> There is a pending patch to standardize all my email addresses in the
> kernel. This patch may conflict with the one in Andrew's tree.
>
> The Email address going forward should be
>
> Christoph Lameter <cl@gentwo.org>
Done. Thanks!
Since the man-pages repo is separate from the kernel, it doesn't
conflict with the kernel one.
Have a lovely day!
Alex
>
>
>
> On Fri, 9 May 2025, Alejandro Colomar wrote:
>
> > Hi all,
> >
> > I've added to BCC everyone whose copyright notices have been removed
> > (those that noted an email). The full thread for this discussion can be
> > found here:
> > <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
> >
> > Please let me know if it's okay to you to transform your copyright
> > notices to make them uniform? That is, do you approve
> > <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> > in what affects you?
> >
> > I've generated the BCC with
> >
> > $ git show 9f2986c34166085225bb5606ebfd4952054e1657 -- man \
> > | grep '^-[^-]' \
> > | grep @ \
> > | grep -o '[^ ]*@[^ ]*' \
> > | sed 's/,//g' \
> > | sed 's/\.$//' \
> > | sed 's/.*(//' \
> > | sed 's/<//' \
> > | sed 's/>//' \
> > | sed 's/\.)//' \
> > | sed 's/)//' \
> > | sort \
> > | uniq \
> > | sed 's/^/Bcc: /';
> >
> >
> > Have a lovely day!
> > Alex
> >
> > On Tue, Apr 08, 2025 at 11:28:29PM +0200, Alejandro Colomar wrote:
> > > Hi Carlos,
> > >
> > > On Tue, Apr 08, 2025 at 04:18:35PM -0400, Carlos O'Donell wrote:
> > > > On 4/8/25 8:42 AM, G. Branden Robinson wrote:
> > > > > Hi Alex,
> > > > >
> > > > > At 2025-04-08T01:05:02+0200, Alejandro Colomar wrote:
> > > > > > On Thu, Feb 13, 2025 at 12:20:58AM +0100, Alejandro Colomar wrote:
> > > > > > > On Wed, Feb 12, 2025 at 05:02:10PM -0600, G. Branden Robinson wrote:
> > > > > > > > If you do this, I suggest you replace these lines with something
> > > > > > > > like:
> > > > > > > >
> > > > > > > > .\" See the Git revision history at
> > > > > > > > .\" $URL
> > > > > > > > .\" for records of changes and contributors to this file.
> > > > > > >
> > > > > > > Good idea.
> > > > > >
> > > > > > I'm thinking I won't do that. I don't want to add that overhead to
> > > > > > each page. People interested in the history of a page will already
> > > > > > have a look at the git history, and there they'll find the old states
> > > > > > of a page, in which they'll find this information.
> > > > > >
> > > > > > And it would require some non-trivial work to add this note
> > > > > > consistently. I'll go with a removal without replacement, I think.
> > > > >
> > > > > Acknowledged. It's been a whole 7 weeks for so, so I don't clearly
> > > > > remember my reasoning from February, but my suggestion may have been at
> > > > > attempt to find a "conservative" alteration to file content or the
> > > > > expressed meaning of the comments.
> > > > >
> > > > > But, what's conservative in one dimension often is not in another, such
> > > > > as "labor required".
> > > > >
> > > > > I also agree that while Git is a complex suite of tools, "git log" is
> > > > > not among its deeper magicks. At least not when run without arguments.
> > > >
> > > > We did something similar in glibc and created a CONTRIBUTED-BY file at the
> > > > top-level and moved all contribution lines out of the respective
> > > > files into the top-level file.
> > >
> > > Yep, a CREDITS file would be interesting. I wouldn't keep info about
> > > which specific files were written by each contributor. That seems
> > > something more appripriate for git-log(1). The pre-git contributions
> > > will be visible in old versions of the pages (i.e., if one sees
> > > Jane Random Developer in CREDITS and wonders which pages she contributed
> > > to, they can `git log -S 'Jane Random Developer'` and similar commands
> > > to find out.
> > >
> > > Thanks!
> > >
> > >
> > > Have a lovely night!
> > > Alex
> > >
> > > >
> > > > e.g.
> > > > ~~~
> > > > The glibc project stopped adding "Contributed by" lines to source files in 2012
> > > > in favour of acknowledging contributors in the glibc manual and through the git
> > > > log. The record of existing "Contributed by" lines have now been moved to this
> > > > file to acknowledge contributions by these developers to glibc.
> > > >
> > > > argp/argp-test.c:
> > > > Written by Miles Bader <miles@gnu.ai.mit.edu>.
> > > >
> > > > argp/tst-argp1.c:
> > > > Contributed by Ulrich Drepper <drepper@redhat.com>, 2002.
> > > > ...
> > > > ~~~
> > > > The top-level CONTRIBUTED-BY has ~3,000 Contributed/Written by lines.
> > > >
> > > > Sme of the authors predated the use of git and so it was simpler to keep the
> > > > lines somewhere as part of the transition away from "Contributed by"-style
> > > > lines.
> > > >
> > > > --
> > > > Cheers,
> > > > Carlos.
> > > >
> > > >
> > >
> > > --
> > > <https://www.alejandro-colomar.es/>
> >
> >
> >
> >
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 12:54 ` Alejandro Colomar
` (8 preceding siblings ...)
2025-05-09 18:22 ` Christoph Lameter (Ampere)
@ 2025-05-09 18:31 ` Christoph Lameter (Ampere)
2025-05-09 19:11 ` Alejandro Colomar
[not found] ` <5681932.rdbgypaU67@sodium>
` (4 subsequent siblings)
14 siblings, 1 reply; 46+ messages in thread
From: Christoph Lameter (Ampere) @ 2025-05-09 18:31 UTC (permalink / raw)
To: Alejandro Colomar; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
Also regarding Andrew Morton's email address: I dont think osdl.org is
still valid. He uses linuxfoundation.org these days.
But you better ask him yourself.
^ permalink raw reply [flat|nested] 46+ messages in thread* Re: Removing in-source contribution records contributer
2025-05-09 18:31 ` Christoph Lameter (Ampere)
@ 2025-05-09 19:11 ` Alejandro Colomar
2025-05-09 21:19 ` Andrew Morton
0 siblings, 1 reply; 46+ messages in thread
From: Alejandro Colomar @ 2025-05-09 19:11 UTC (permalink / raw)
To: Christoph Lameter (Ampere), Andrew Morton
Cc: linux-man, Carlos O'Donell, G. Branden Robinson
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
On Fri, May 09, 2025 at 11:31:58AM -0700, Christoph Lameter (Ampere) wrote:
>
> Also regarding Andrew Morton's email address: I dont think osdl.org is
> still valid. He uses linuxfoundation.org these days.
> But you better ask him yourself.
Hi Christoph, Andrew,
Thanks! I've bounced the original mail to him. Andrew, I guess I
should use your LF address for the AUTHORS file, right?
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 19:11 ` Alejandro Colomar
@ 2025-05-09 21:19 ` Andrew Morton
2025-05-09 21:25 ` Alejandro Colomar
0 siblings, 1 reply; 46+ messages in thread
From: Andrew Morton @ 2025-05-09 21:19 UTC (permalink / raw)
To: Alejandro Colomar
Cc: Christoph Lameter (Ampere), linux-man, Carlos O'Donell,
G. Branden Robinson
On Fri, 9 May 2025 21:11:50 +0200 Alejandro Colomar <alx@kernel.org> wrote:
> On Fri, May 09, 2025 at 11:31:58AM -0700, Christoph Lameter (Ampere) wrote:
> >
> > Also regarding Andrew Morton's email address: I dont think osdl.org is
> > still valid. He uses linuxfoundation.org these days.
> > But you better ask him yourself.
>
> Hi Christoph, Andrew,
>
> Thanks! I've bounced the original mail to him. Andrew, I guess I
> should use your LF address for the AUTHORS file, right?
@osdl.org @linuxfoundation.org @linux-foundation.org @linux.com
@kernel.org all work. I normally use (the outdated) @linux-foundation.org
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 21:19 ` Andrew Morton
@ 2025-05-09 21:25 ` Alejandro Colomar
0 siblings, 0 replies; 46+ messages in thread
From: Alejandro Colomar @ 2025-05-09 21:25 UTC (permalink / raw)
To: Andrew Morton
Cc: Christoph Lameter (Ampere), linux-man, Carlos O'Donell,
G. Branden Robinson
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Hi Andrew,
On Fri, May 09, 2025 at 02:19:35PM -0700, Andrew Morton wrote:
> On Fri, 9 May 2025 21:11:50 +0200 Alejandro Colomar <alx@kernel.org> wrote:
>
> > On Fri, May 09, 2025 at 11:31:58AM -0700, Christoph Lameter (Ampere) wrote:
> > >
> > > Also regarding Andrew Morton's email address: I dont think osdl.org is
> > > still valid. He uses linuxfoundation.org these days.
> > > But you better ask him yourself.
> >
> > Hi Christoph, Andrew,
> >
> > Thanks! I've bounced the original mail to him. Andrew, I guess I
> > should use your LF address for the AUTHORS file, right?
>
> @osdl.org @linuxfoundation.org @linux-foundation.org @linux.com
> @kernel.org all work. I normally use (the outdated) @linux-foundation.org
Do you expect any one to survive the others? I guess I should use
whichever would last more. If you have no preference, I'll just leave
it untouched.
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 46+ messages in thread
[parent not found: <5681932.rdbgypaU67@sodium>]
* Re: Removing in-source contribution records contributer
[not found] ` <5681932.rdbgypaU67@sodium>
@ 2025-05-10 11:02 ` Alejandro Colomar
0 siblings, 0 replies; 46+ messages in thread
From: Alejandro Colomar @ 2025-05-10 11:02 UTC (permalink / raw)
To: Oron Peled; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
Hi Oron,
On Sat, May 10, 2025 at 02:37:52AM +0300, Oron Peled wrote:
> Hi,
>
> I've no objection to the change.
> Only after I searched the list I recalled there was some "boot.7" man page I wrote many years ago.
:-)
> So this change actually promote me to a "contributor to the Linux
> man-pages project", instead of someone that wrote a small and
> unimportant man-page years ago ;-)
>
> Thank you, the real contributors that are maintaining this for years.
IMO, you and many like you are as real contributors as the maintainers.
The project wouldn't be what it is without those many small
contributions.
Have a lovely day!
Alex
> --
> Oron Peled
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 46+ messages in thread
* Re: Removing in-source contribution records contributer
2025-05-09 12:54 ` Alejandro Colomar
` (10 preceding siblings ...)
[not found] ` <5681932.rdbgypaU67@sodium>
@ 2025-05-12 7:58 ` Sean Young
2025-05-12 18:51 ` Stefan Hajnoczi
` (2 subsequent siblings)
14 siblings, 0 replies; 46+ messages in thread
From: Sean Young @ 2025-05-12 7:58 UTC (permalink / raw)
To: Alejandro Colomar; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
On Fri, May 09, 2025 at 02:54:31PM +0200, Alejandro Colomar wrote:
> Hi all,
>
> I've added to BCC everyone whose copyright notices have been removed
> (those that noted an email). The full thread for this discussion can be
> found here:
> <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
>
> Please let me know if it's okay to you to transform your copyright
> notices to make them uniform? That is, do you approve
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> in what affects you?
The normal way to do this is a Signed-off-by on a public list and then
collect those into the commit.
Sure I am okay with this but I don't see the point of this "process",
where agreements just collect in your mailboxes.
Sean
>
> I've generated the BCC with
>
> $ git show 9f2986c34166085225bb5606ebfd4952054e1657 -- man \
> | grep '^-[^-]' \
> | grep @ \
> | grep -o '[^ ]*@[^ ]*' \
> | sed 's/,//g' \
> | sed 's/\.$//' \
> | sed 's/.*(//' \
> | sed 's/<//' \
> | sed 's/>//' \
> | sed 's/\.)//' \
> | sed 's/)//' \
> | sort \
> | uniq \
> | sed 's/^/Bcc: /';
>
>
> Have a lovely day!
> Alex
>
> On Tue, Apr 08, 2025 at 11:28:29PM +0200, Alejandro Colomar wrote:
> > Hi Carlos,
> >
> > On Tue, Apr 08, 2025 at 04:18:35PM -0400, Carlos O'Donell wrote:
> > > On 4/8/25 8:42 AM, G. Branden Robinson wrote:
> > > > Hi Alex,
> > > >
> > > > At 2025-04-08T01:05:02+0200, Alejandro Colomar wrote:
> > > > > On Thu, Feb 13, 2025 at 12:20:58AM +0100, Alejandro Colomar wrote:
> > > > > > On Wed, Feb 12, 2025 at 05:02:10PM -0600, G. Branden Robinson wrote:
> > > > > > > If you do this, I suggest you replace these lines with something
> > > > > > > like:
> > > > > > >
> > > > > > > .\" See the Git revision history at
> > > > > > > .\" $URL
> > > > > > > .\" for records of changes and contributors to this file.
> > > > > >
> > > > > > Good idea.
> > > > >
> > > > > I'm thinking I won't do that. I don't want to add that overhead to
> > > > > each page. People interested in the history of a page will already
> > > > > have a look at the git history, and there they'll find the old states
> > > > > of a page, in which they'll find this information.
> > > > >
> > > > > And it would require some non-trivial work to add this note
> > > > > consistently. I'll go with a removal without replacement, I think.
> > > >
> > > > Acknowledged. It's been a whole 7 weeks for so, so I don't clearly
> > > > remember my reasoning from February, but my suggestion may have been at
> > > > attempt to find a "conservative" alteration to file content or the
> > > > expressed meaning of the comments.
> > > >
> > > > But, what's conservative in one dimension often is not in another, such
> > > > as "labor required".
> > > >
> > > > I also agree that while Git is a complex suite of tools, "git log" is
> > > > not among its deeper magicks. At least not when run without arguments.
> > >
> > > We did something similar in glibc and created a CONTRIBUTED-BY file at the
> > > top-level and moved all contribution lines out of the respective
> > > files into the top-level file.
> >
> > Yep, a CREDITS file would be interesting. I wouldn't keep info about
> > which specific files were written by each contributor. That seems
> > something more appripriate for git-log(1). The pre-git contributions
> > will be visible in old versions of the pages (i.e., if one sees
> > Jane Random Developer in CREDITS and wonders which pages she contributed
> > to, they can `git log -S 'Jane Random Developer'` and similar commands
> > to find out.
> >
> > Thanks!
> >
> >
> > Have a lovely night!
> > Alex
> >
> > >
> > > e.g.
> > > ~~~
> > > The glibc project stopped adding "Contributed by" lines to source files in 2012
> > > in favour of acknowledging contributors in the glibc manual and through the git
> > > log. The record of existing "Contributed by" lines have now been moved to this
> > > file to acknowledge contributions by these developers to glibc.
> > >
> > > argp/argp-test.c:
> > > Written by Miles Bader <miles@gnu.ai.mit.edu>.
> > >
> > > argp/tst-argp1.c:
> > > Contributed by Ulrich Drepper <drepper@redhat.com>, 2002.
> > > ...
> > > ~~~
> > > The top-level CONTRIBUTED-BY has ~3,000 Contributed/Written by lines.
> > >
> > > Sme of the authors predated the use of git and so it was simpler to keep the
> > > lines somewhere as part of the transition away from "Contributed by"-style
> > > lines.
> > >
> > > --
> > > Cheers,
> > > Carlos.
> > >
> > >
> >
> > --
> > <https://www.alejandro-colomar.es/>
>
>
>
> --
> <https://www.alejandro-colomar.es/>
^ permalink raw reply [flat|nested] 46+ messages in thread* Re: Removing in-source contribution records contributer
2025-05-09 12:54 ` Alejandro Colomar
` (11 preceding siblings ...)
2025-05-12 7:58 ` Sean Young
@ 2025-05-12 18:51 ` Stefan Hajnoczi
2025-05-12 19:03 ` Thomas Gleixner
2025-05-19 7:40 ` Florent Revest
14 siblings, 0 replies; 46+ messages in thread
From: Stefan Hajnoczi @ 2025-05-12 18:51 UTC (permalink / raw)
To: Alejandro Colomar; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
[-- Attachment #1: Type: text/plain, Size: 4683 bytes --]
On Fri, May 09, 2025 at 02:54:31PM +0200, Alejandro Colomar wrote:
> Hi all,
>
> I've added to BCC everyone whose copyright notices have been removed
> (those that noted an email). The full thread for this discussion can be
> found here:
> <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
>
> Please let me know if it's okay to you to transform your copyright
> notices to make them uniform? That is, do you approve
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> in what affects you?
Hi Alejandro,
I approve. Thanks!
Stefan
>
> I've generated the BCC with
>
> $ git show 9f2986c34166085225bb5606ebfd4952054e1657 -- man \
> | grep '^-[^-]' \
> | grep @ \
> | grep -o '[^ ]*@[^ ]*' \
> | sed 's/,//g' \
> | sed 's/\.$//' \
> | sed 's/.*(//' \
> | sed 's/<//' \
> | sed 's/>//' \
> | sed 's/\.)//' \
> | sed 's/)//' \
> | sort \
> | uniq \
> | sed 's/^/Bcc: /';
>
>
> Have a lovely day!
> Alex
>
> On Tue, Apr 08, 2025 at 11:28:29PM +0200, Alejandro Colomar wrote:
> > Hi Carlos,
> >
> > On Tue, Apr 08, 2025 at 04:18:35PM -0400, Carlos O'Donell wrote:
> > > On 4/8/25 8:42 AM, G. Branden Robinson wrote:
> > > > Hi Alex,
> > > >
> > > > At 2025-04-08T01:05:02+0200, Alejandro Colomar wrote:
> > > > > On Thu, Feb 13, 2025 at 12:20:58AM +0100, Alejandro Colomar wrote:
> > > > > > On Wed, Feb 12, 2025 at 05:02:10PM -0600, G. Branden Robinson wrote:
> > > > > > > If you do this, I suggest you replace these lines with something
> > > > > > > like:
> > > > > > >
> > > > > > > .\" See the Git revision history at
> > > > > > > .\" $URL
> > > > > > > .\" for records of changes and contributors to this file.
> > > > > >
> > > > > > Good idea.
> > > > >
> > > > > I'm thinking I won't do that. I don't want to add that overhead to
> > > > > each page. People interested in the history of a page will already
> > > > > have a look at the git history, and there they'll find the old states
> > > > > of a page, in which they'll find this information.
> > > > >
> > > > > And it would require some non-trivial work to add this note
> > > > > consistently. I'll go with a removal without replacement, I think.
> > > >
> > > > Acknowledged. It's been a whole 7 weeks for so, so I don't clearly
> > > > remember my reasoning from February, but my suggestion may have been at
> > > > attempt to find a "conservative" alteration to file content or the
> > > > expressed meaning of the comments.
> > > >
> > > > But, what's conservative in one dimension often is not in another, such
> > > > as "labor required".
> > > >
> > > > I also agree that while Git is a complex suite of tools, "git log" is
> > > > not among its deeper magicks. At least not when run without arguments.
> > >
> > > We did something similar in glibc and created a CONTRIBUTED-BY file at the
> > > top-level and moved all contribution lines out of the respective
> > > files into the top-level file.
> >
> > Yep, a CREDITS file would be interesting. I wouldn't keep info about
> > which specific files were written by each contributor. That seems
> > something more appripriate for git-log(1). The pre-git contributions
> > will be visible in old versions of the pages (i.e., if one sees
> > Jane Random Developer in CREDITS and wonders which pages she contributed
> > to, they can `git log -S 'Jane Random Developer'` and similar commands
> > to find out.
> >
> > Thanks!
> >
> >
> > Have a lovely night!
> > Alex
> >
> > >
> > > e.g.
> > > ~~~
> > > The glibc project stopped adding "Contributed by" lines to source files in 2012
> > > in favour of acknowledging contributors in the glibc manual and through the git
> > > log. The record of existing "Contributed by" lines have now been moved to this
> > > file to acknowledge contributions by these developers to glibc.
> > >
> > > argp/argp-test.c:
> > > Written by Miles Bader <miles@gnu.ai.mit.edu>.
> > >
> > > argp/tst-argp1.c:
> > > Contributed by Ulrich Drepper <drepper@redhat.com>, 2002.
> > > ...
> > > ~~~
> > > The top-level CONTRIBUTED-BY has ~3,000 Contributed/Written by lines.
> > >
> > > Sme of the authors predated the use of git and so it was simpler to keep the
> > > lines somewhere as part of the transition away from "Contributed by"-style
> > > lines.
> > >
> > > --
> > > Cheers,
> > > Carlos.
> > >
> > >
> >
> > --
> > <https://www.alejandro-colomar.es/>
>
>
>
> --
> <https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 46+ messages in thread* Re: Removing in-source contribution records contributer
2025-05-09 12:54 ` Alejandro Colomar
` (12 preceding siblings ...)
2025-05-12 18:51 ` Stefan Hajnoczi
@ 2025-05-12 19:03 ` Thomas Gleixner
2025-05-19 7:40 ` Florent Revest
14 siblings, 0 replies; 46+ messages in thread
From: Thomas Gleixner @ 2025-05-12 19:03 UTC (permalink / raw)
To: Alejandro Colomar, linux-man; +Cc: Carlos O'Donell, G. Branden Robinson
On Fri, May 09 2025 at 14:54, Alejandro Colomar wrote:
> Hi all,
>
> I've added to BCC everyone whose copyright notices have been removed
> (those that noted an email). The full thread for this discussion can be
> found here:
> <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
>
> Please let me know if it's okay to you to transform your copyright
> notices to make them uniform? That is, do you approve
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> in what affects you?
Acked-by: Thomas Gleixner <tglx@linutronix.de>
^ permalink raw reply [flat|nested] 46+ messages in thread* Re: Removing in-source contribution records contributer
2025-05-09 12:54 ` Alejandro Colomar
` (13 preceding siblings ...)
2025-05-12 19:03 ` Thomas Gleixner
@ 2025-05-19 7:40 ` Florent Revest
14 siblings, 0 replies; 46+ messages in thread
From: Florent Revest @ 2025-05-19 7:40 UTC (permalink / raw)
To: Alejandro Colomar; +Cc: linux-man, Carlos O'Donell, G. Branden Robinson
On Fri, May 9, 2025 at 2:55 PM Alejandro Colomar <alx@kernel.org> wrote:
>
> Hi all,
>
> I've added to BCC everyone whose copyright notices have been removed
> (those that noted an email). The full thread for this discussion can be
> found here:
> <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
>
> Please let me know if it's okay to you to transform your copyright
> notices to make them uniform? That is, do you approve
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=9f2986c34166085225bb5606ebfd4952054e1657>
> in what affects you?
Yes. Thank you!
> I've generated the BCC with
>
> $ git show 9f2986c34166085225bb5606ebfd4952054e1657 -- man \
> | grep '^-[^-]' \
> | grep @ \
> | grep -o '[^ ]*@[^ ]*' \
> | sed 's/,//g' \
> | sed 's/\.$//' \
> | sed 's/.*(//' \
> | sed 's/<//' \
> | sed 's/>//' \
> | sed 's/\.)//' \
> | sed 's/)//' \
> | sort \
> | uniq \
> | sed 's/^/Bcc: /';
>
>
> Have a lovely day!
> Alex
>
> On Tue, Apr 08, 2025 at 11:28:29PM +0200, Alejandro Colomar wrote:
> > Hi Carlos,
> >
> > On Tue, Apr 08, 2025 at 04:18:35PM -0400, Carlos O'Donell wrote:
> > > On 4/8/25 8:42 AM, G. Branden Robinson wrote:
> > > > Hi Alex,
> > > >
> > > > At 2025-04-08T01:05:02+0200, Alejandro Colomar wrote:
> > > > > On Thu, Feb 13, 2025 at 12:20:58AM +0100, Alejandro Colomar wrote:
> > > > > > On Wed, Feb 12, 2025 at 05:02:10PM -0600, G. Branden Robinson wrote:
> > > > > > > If you do this, I suggest you replace these lines with something
> > > > > > > like:
> > > > > > >
> > > > > > > .\" See the Git revision history at
> > > > > > > .\" $URL
> > > > > > > .\" for records of changes and contributors to this file.
> > > > > >
> > > > > > Good idea.
> > > > >
> > > > > I'm thinking I won't do that. I don't want to add that overhead to
> > > > > each page. People interested in the history of a page will already
> > > > > have a look at the git history, and there they'll find the old states
> > > > > of a page, in which they'll find this information.
> > > > >
> > > > > And it would require some non-trivial work to add this note
> > > > > consistently. I'll go with a removal without replacement, I think.
> > > >
> > > > Acknowledged. It's been a whole 7 weeks for so, so I don't clearly
> > > > remember my reasoning from February, but my suggestion may have been at
> > > > attempt to find a "conservative" alteration to file content or the
> > > > expressed meaning of the comments.
> > > >
> > > > But, what's conservative in one dimension often is not in another, such
> > > > as "labor required".
> > > >
> > > > I also agree that while Git is a complex suite of tools, "git log" is
> > > > not among its deeper magicks. At least not when run without arguments.
> > >
> > > We did something similar in glibc and created a CONTRIBUTED-BY file at the
> > > top-level and moved all contribution lines out of the respective
> > > files into the top-level file.
> >
> > Yep, a CREDITS file would be interesting. I wouldn't keep info about
> > which specific files were written by each contributor. That seems
> > something more appripriate for git-log(1). The pre-git contributions
> > will be visible in old versions of the pages (i.e., if one sees
> > Jane Random Developer in CREDITS and wonders which pages she contributed
> > to, they can `git log -S 'Jane Random Developer'` and similar commands
> > to find out.
> >
> > Thanks!
> >
> >
> > Have a lovely night!
> > Alex
> >
> > >
> > > e.g.
> > > ~~~
> > > The glibc project stopped adding "Contributed by" lines to source files in 2012
> > > in favour of acknowledging contributors in the glibc manual and through the git
> > > log. The record of existing "Contributed by" lines have now been moved to this
> > > file to acknowledge contributions by these developers to glibc.
> > >
> > > argp/argp-test.c:
> > > Written by Miles Bader <miles@gnu.ai.mit.edu>.
> > >
> > > argp/tst-argp1.c:
> > > Contributed by Ulrich Drepper <drepper@redhat.com>, 2002.
> > > ...
> > > ~~~
> > > The top-level CONTRIBUTED-BY has ~3,000 Contributed/Written by lines.
> > >
> > > Sme of the authors predated the use of git and so it was simpler to keep the
> > > lines somewhere as part of the transition away from "Contributed by"-style
> > > lines.
> > >
> > > --
> > > Cheers,
> > > Carlos.
> > >
> > >
> >
> > --
> > <https://www.alejandro-colomar.es/>
>
>
>
> --
> <https://www.alejandro-colomar.es/>
^ permalink raw reply [flat|nested] 46+ messages in thread