From: Efraim Flashner <efraim@flashner.co.il>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 38815@debbugs.gnu.org
Subject: [bug#38815] guix-patches@ recorded as commit author (was: sassc: Update to 3.6.1.)
Date: Thu, 9 Jan 2020 21:54:34 +0200 [thread overview]
Message-ID: <20200109195434.GA1370@E5400> (raw)
In-Reply-To: <871rs9evug.fsf@nckx>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
On Wed, Jan 08, 2020 at 05:50:15PM +0100, Tobias Geerinckx-Rice via Guix-patches via wrote:
> Riku, Efraim, Guix,
>
> I noticed that this commit and the preceding libsass update have an
> incorrect author e-mail addres:
>
> commit fc4eb87dc45b169e3912c73bbf60cb8ce76b7c7c
> Author: Riku Viitanen via Guix-patches via <guix-patches@gnu.org>
>
> The actual patch posted to guix-patches[0] has two correct From: lines.
>
> Does anyone know what happened here? And how it could be avoided? Is the
> Web interface hiding anything strange about these messages?
I caught one another time but this time they slipped through. I normally
patch the pipe directly from mutt to 'cd workspace/guix; git am -S -s'.
>
> Would a git hook to catch suspect addresses be a good idea?
>
Probably couldn't hurt.
> Kind regards,
>
> T G-R
>
> [0]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38815
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-01-09 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 15:09 [bug#38815] [PATCH] gnu: sassc: Update to 3.6.1 Riku Viitanen via Guix-patches via
2019-12-30 18:21 ` bug#38815: " Efraim Flashner
2020-01-08 16:50 ` [bug#38815] guix-patches@ recorded as commit author (was: sassc: Update to 3.6.1.) Tobias Geerinckx-Rice via Guix-patches via
2020-01-09 19:54 ` Efraim Flashner [this message]
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=20200109195434.GA1370@E5400 \
--to=efraim@flashner.co.il \
--cc=38815@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.