From: Stefan Hajnoczi <stefanha@redhat.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, Carlos O'Donell <carlos@redhat.com>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: Removing in-source contribution records contributer
Date: Mon, 12 May 2025 14:51:59 -0400 [thread overview]
Message-ID: <20250512185159.GJ141177@fedora> (raw)
In-Reply-To: <2tmwbk6ennuamcvjdqnialvh4ez3zen666qatcklevasimlihu@n7o5hp6aejqp>
[-- 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 --]
next prev parent reply other threads:[~2025-05-12 18:52 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1739389071.git.amitpinhass@gmail.com>
2025-02-12 19:39 ` [PATCH v2 2/2] [PATCH v2] man/man2/kill.2: Add Amit Pinhas as a contributer Amit Pinhas
2025-02-12 20:26 ` Alejandro Colomar
2025-02-12 23:02 ` G. Branden Robinson
2025-02-12 23:20 ` Removing in-source contribution records contributer Alejandro Colomar
2025-04-07 23:05 ` Alejandro Colomar
2025-04-08 12:42 ` G. Branden Robinson
2025-04-08 20:18 ` Carlos O'Donell
2025-04-08 21:28 ` Alejandro Colomar
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:31 ` Alejandro Colomar
2025-05-09 13:39 ` Josef Bacik
2025-05-09 13:50 ` наб
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:48 ` G. Branden Robinson
2025-05-09 15:43 ` Dave Martin
2025-05-09 18:49 ` Alejandro Colomar
2025-05-09 19:07 ` Alejandro Colomar
2025-05-12 11:40 ` Dave Martin
2025-05-09 14:16 ` Heinrich Schuchardt
2025-05-09 15:13 ` Tycho Andersen
2025-05-09 18:35 ` Alejandro Colomar
2025-05-09 20:56 ` Tycho Andersen
2025-05-09 21:11 ` Alejandro Colomar
2025-05-10 22:24 ` 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)
2025-05-09 19:11 ` Alejandro Colomar
2025-05-09 21:19 ` Andrew Morton
2025-05-09 21:25 ` Alejandro Colomar
[not found] ` <5681932.rdbgypaU67@sodium>
2025-05-10 11:02 ` Alejandro Colomar
2025-05-12 7:58 ` Sean Young
2025-05-12 18:51 ` Stefan Hajnoczi [this message]
2025-05-12 19:03 ` Thomas Gleixner
2025-05-19 7:40 ` Florent Revest
2025-04-08 18:00 ` Eugene Syromyatnikov
2025-04-08 21:25 ` Alejandro Colomar
2025-04-09 21:15 ` Carlos O'Donell
2025-04-09 23:25 ` Alejandro Colomar
2025-05-05 22:51 ` Alejandro Colomar
2025-05-06 9:22 ` Eugene Syromyatnikov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250512185159.GJ141177@fedora \
--to=stefanha@redhat.com \
--cc=alx@kernel.org \
--cc=carlos@redhat.com \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.