Re: Removing in-source contribution records contributer

Alejandro Colomar
2025-05-09T13:31:40Z

[-- 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/>