From: Tycho Andersen <tycho@tycho.pizza>
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: Fri, 9 May 2025 14:56:01 -0600 [thread overview]
Message-ID: <aB5r4YOVpW5rNKL5@tycho.pizza> (raw)
In-Reply-To: <vaja6de7wo5lbdf7nephc4eb5xpx4nhwv6y6nkdbppry7qz22r@6jw3zqipjunn>
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
next prev parent reply other threads:[~2025-05-09 20:56 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 [this message]
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
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=aB5r4YOVpW5rNKL5@tycho.pizza \
--to=tycho@tycho.pizza \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox