From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: guix-devel@gnu.org, Andreas Enge <andreas@enge.fr>,
Pierre Langlois <pierre.langlois@gmx.com>
Subject: Re: Core-updates merge
Date: Fri, 14 Jul 2023 09:52:28 -0700 [thread overview]
Message-ID: <CAFHYt57GNTbvQ4ai6GDQ0i8-m10m9_D1YcUefcXUHE59NdOdqw@mail.gmail.com> (raw)
In-Reply-To: <87edla1md1.fsf@protonmail.com>
Hi John,
On Fri, Jul 14, 2023 at 9:37 AM John Kehayias
<john.kehayias@protonmail.com> wrote:
>
> Unfortunately
> I managed to clobber the author line in the git log after editing and
> testing locally, sorry about that! (Anything that can be done to fix
> that?)
Giving proper attribution can be essential in group projects. You
could revert your commit and then re-commit the change with the
correct author.
How to handle it best depends on your dynamics with the injured party.
I personally never cared enough—especially not in the case of an
innocent mistake—but I know that some folks feel strongly about being
made whole.
Kind regards
Felix
next prev parent reply other threads:[~2023-07-14 16:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 16:36 Core-updates merge John Kehayias
2023-07-14 16:52 ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
2023-07-14 21:26 ` John Kehayias
2023-07-14 18:12 ` Pierre Langlois
2023-07-14 21:31 ` John Kehayias
2023-07-14 21:37 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
-- strict thread matches above, loose matches on Subject: below --
2023-04-25 14:09 Andreas Enge
2023-04-25 14:40 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-04-25 14:57 ` Katherine Cox-Buday
2023-04-25 19:27 ` Maxim Cournoyer
2023-04-25 15:31 ` Josselin Poiret
2023-04-25 16:09 ` Leo Famulari
2023-05-03 21:07 ` Ludovic Courtès
2023-04-28 5:55 ` John Kehayias
2023-04-28 14:17 ` Simon Tournier
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=CAFHYt57GNTbvQ4ai6GDQ0i8-m10m9_D1YcUefcXUHE59NdOdqw@mail.gmail.com \
--to=guix-devel@gnu.org \
--cc=andreas@enge.fr \
--cc=felix.lechner@lease-up.com \
--cc=john.kehayias@protonmail.com \
--cc=pierre.langlois@gmx.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.