From: Julien Lepiller <julien@lepiller.eu>
To: Thiago Jung Bauermann <bauermann@kolabnow.com>
Cc: 57188-done@debbugs.gnu.org
Subject: [bug#57188] [PATCH] news: Add 'pt' translation.
Date: Mon, 15 Aug 2022 07:25:11 +0200 [thread overview]
Message-ID: <4051D4C3-065A-4B37-9C2C-6E825355F9B8@lepiller.eu> (raw)
In-Reply-To: <87r11ijgo2.fsf@kolabnow.com>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
Arg, I'm so sorry :/ I should have paid more attention.
Le 15 août 2022 05:55:14 GMT+02:00, Thiago Jung Bauermann <bauermann@kolabnow.com> a écrit :
>
>Hello Julien,
>
>Julien Lepiller <julien@lepiller.eu> writes:
>
>> Pushed to master as ca8c7a36dfbefd66841a2a6df4c9e44ba525c3e0, thank you!
>
>Thank you! And thanks for committing it so quickly.
>
>Just a small nit, I hope you won't mind me mentioning it:
>
>in the commit, the author field ended up as:
>
> Author: Thiago Jung Bauermann via Guix-patches via <guix-patches@gnu.org>
>
>which is wrong. It should have been:
>
> Author: Thiago Jung Bauermann <bauermann@kolabnow.com>
>
>IMHO correct attribution of a contribution is important, and the email
>address is an important part of a free software contributor's online
>identity.
>
>I don't actually mind in this case because most of my patches to Guix
>were committed with the correct address but if this was my first
>accepted patch in the project, or if all of my patches had this author
>identification, then I would have felt differently.
>
>--
>Thanks
>Thiago
[-- Attachment #2: Type: text/html, Size: 1588 bytes --]
next prev parent reply other threads:[~2022-08-15 5:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 21:51 [bug#57188] [PATCH] news: Add 'pt' translation Thiago Jung Bauermann via Guix-patches via
2022-08-14 6:52 ` bug#57188: " Julien Lepiller
2022-08-15 3:55 ` [bug#57188] " Thiago Jung Bauermann via Guix-patches via
2022-08-15 5:25 ` Julien Lepiller [this message]
2022-08-16 3:37 ` Thiago Jung Bauermann via Guix-patches via
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=4051D4C3-065A-4B37-9C2C-6E825355F9B8@lepiller.eu \
--to=julien@lepiller.eu \
--cc=57188-done@debbugs.gnu.org \
--cc=bauermann@kolabnow.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.