From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:43775) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ipEXv-0000nN-Jj for guix-patches@gnu.org; Wed, 08 Jan 2020 11:51:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ipEXu-0007JY-Di for guix-patches@gnu.org; Wed, 08 Jan 2020 11:51:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:45254) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ipEXu-0007J5-5W for guix-patches@gnu.org; Wed, 08 Jan 2020 11:51:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ipEXu-0003FD-4w for guix-patches@gnu.org; Wed, 08 Jan 2020 11:51:02 -0500 Subject: [bug#38815] guix-patches@ recorded as commit author (was: sassc: Update to 3.6.1.) References: <8vPKTnwwfY4ecgts67qtXbG04xMreq2Oy8kmlI0Oix7RgxCHkExOcA79B4rjUq2i7Mu-lHpji6XXRy6DBWx9MOdZkhqvB6flKffTjO3wyr8=@protonmail.com> In-Reply-To: <8vPKTnwwfY4ecgts67qtXbG04xMreq2Oy8kmlI0Oix7RgxCHkExOcA79B4rjUq2i7Mu-lHpji6XXRy6DBWx9MOdZkhqvB6flKffTjO3wyr8=@protonmail.com> Resent-Message-ID: Date: Wed, 08 Jan 2020 17:50:15 +0100 Message-ID: <871rs9evug.fsf@nckx> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" Reply-to: Tobias Geerinckx-Rice , Tobias Geerinckx-Rice via Guix-patches From: Tobias Geerinckx-Rice via Guix-patches via To: 38815@debbugs.gnu.org --=-=-= Content-Type: text/plain; format=flowed 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 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? Would a git hook to catch suspect addresses be a good idea? Kind regards, T G-R [0]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38815 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEfo+u0AlEeO9y5k0W2Imw8BjFSTwFAl4WCEcACgkQ2Imw8BjF STyCehAAlHXbjUO2ov41sRxWvTKp/DbAdciPNQU5KJc9U+m0W7q82cGOFpqXl6/A fZn0z4/oWyRQAL3GrToiGZ76MXynH4849s331aawXYNSG8GY+LyVKWUp5Ueswjnp K08V6umfZX36KxLP7m7TMdILzGlwwIZp9S/vZU6gPQ/3cCp/npNNqF1Pq+VMLZpW IL49pOb5pot2W+tCDVlNuKaO7+QBz5S+6SLrw0N/HUxHKou4ieExVGPYdLTrQcj0 xoxigKAq6giOMQ8x1sQtg1fVHBj0A1nJJYc9sJC3Ea9O7wFLSbkSxYLmhqRdKHsO TMh3fMccQrbBwgJhOPNN2900YFu5MJipyr/KrVr2dASO8UJaoss4+CA1xnfu48/+ Ri4bWzEi666y8k34/w8Fc4ChmWKo+tnjuSB1ID0RT/5bMQsizVaLhaNa8UvaInlA h8oLyjU+qqlbOFXzxTppK361uJjTSngCupXTQVKA4cCwDvvolUo08uxmg2ZplgTK GGEK/LicUxMNR446JNWhjCHKKcLsn6pNkcmOOSjTmOl/Dk3IY9DaYvxPsUIXsiT7 eciPc6J25cfkv63M5T95yekuscskPU6HrZLTPSMcV0hIbt4zCDb1lO1r1eom9Z+y 7jdnxeaCm3vbJEbgbL8oGS7n3q8WkLSxu7N+NAycZMxa8IITa2A= =0udm -----END PGP SIGNATURE----- --=-=-=--