From: Tomas Volf <~@wolfsden.cz>
To: guix-devel@gnu.org
Subject: Re: 01/04: gnu: libtorrent-rasterbar: Update to 2.0.10.
Date: Sun, 06 Oct 2024 19:52:21 +0200 [thread overview]
Message-ID: <87y131xgoa.fsf@wolfsden.cz> (raw)
In-Reply-To: <20241006090321.C8D6A1C1D84@vcs3.savannah.gnu.org> (guix-commits@gnu.org's message of "Sun, 6 Oct 2024 05:03:21 -0400 (EDT)")
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
guix-commits@gnu.org writes:
> z572 pushed a commit to branch master
> in repository guix.
>
> commit 37dede4c4d8c25a786f2a2e2a17ba54b4ba6283f
> Author: Adam Faiz via Guix-patches via <guix-patches@gnu.org>
> AuthorDate: Tue Aug 6 21:07:40 2024 +0800
I have to admit I am not very happy regarding the change in the commit
author. While I understand the change itself might have been somewhat
trivial, I did work with upstream to merge the required changes for
2.0.10, so having the authorship stolen like this leaves somewhat
unpleasant feeling.
Especially since applying for commit access has a number of commits as
one of prerequisites, having your address visible in `git log --author'
goes from "collecting internet points" into "actually somewhat
important". But even without that, I would still consider it not a nice
thing to do.
Have a nice day,
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]
next parent reply other threads:[~2024-10-06 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <172820540113.1389510.12193329113919899297@vcs3.savannah.gnu.org>
[not found] ` <20241006090321.C8D6A1C1D84@vcs3.savannah.gnu.org>
2024-10-06 17:52 ` Tomas Volf [this message]
2024-10-06 18:16 ` 01/04: gnu: libtorrent-rasterbar: Update to 2.0.10 Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-10-06 19:15 ` [bug#69276] " John Kehayias via Guix-patches via
2024-10-06 22:02 ` Tomas Volf
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y131xgoa.fsf@wolfsden.cz \
--to=~@wolfsden.cz \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).