From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50971) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dg3tW-0001ut-5e for guix-patches@gnu.org; Fri, 11 Aug 2017 02:58:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dg3tS-0000Tt-9T for guix-patches@gnu.org; Fri, 11 Aug 2017 02:58:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:46382) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dg3tS-0000Tp-4j for guix-patches@gnu.org; Fri, 11 Aug 2017 02:58:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dg3tR-0003zJ-SY for guix-patches@gnu.org; Fri, 11 Aug 2017 02:58:01 -0400 Subject: [bug#28020] [PATCH] gnu: Add emacs-gitpatch. Resent-Message-ID: Date: Fri, 11 Aug 2017 06:56:46 +0000 From: ng0 Message-ID: <20170811065646.26egherqrbecpend@abyayala> References: <87wp6ekkef.fsf@gmail.com> <4b50a45a.ADkAACnAL5YAAAAAAAAAAAPejtMAAAACwQwAAAAAAAW9WABZjCOA@mailjet.com> <20170810120612.bi33kbdswgtktohr@abyayala> <20170810165517.nojmfy7j4busmwao@abyayala> <4c62b87d.AEQAOV3jPRsAAAAAAAAAAAPU2QkAAAACwQwAAAAAAAW9WABZjJhx@mailjet.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="u6c734qvleouuetg" Content-Disposition: inline In-Reply-To: <4c62b87d.AEQAOV3jPRsAAAAAAAAAAAPU2QkAAAACwQwAAAAAAAW9WABZjJhx@mailjet.com> 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" To: Arun Isaac Cc: 28020-done@debbugs.gnu.org --u6c734qvleouuetg Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Arun Isaac transcribed 0.7K bytes: >=20 > > it would be nice to have a checker for this somehow... >=20 > Yes, something like `guix lint', but for commits. It should become a git > hook much like etc/git/pre-push. >=20 > I'll write this checker script. I could write one specifically looking > for the kind of mistake I made -- the problem with part of the email > thread coming into the commit message. But, I think it will be better to > have a more general checker. Any suggestions to get started? What are > the other kind of mistakes that have happened in the commit log? The other one I remember right now is debbugs leaking into the subject if you are not careful. Happened at least once, search for "bug#" in the log. It's a rare unfixed thing, take a look at d54db52e7fe469612386ec15d4bf7650e9225a92 and how it came to be. Someone else complained about this happening with debbugs. --=20 ng0 GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588 GnuPG: https://n0is.noblogs.org/my-keys https://www.infotropique.org https://krosos.org --u6c734qvleouuetg Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlmNVS4ACgkQ4i+bv+40 hYgM/w/9HovVwzQAqv4APqsC2cmv7U/aJlmQvU7gYcMz0HWcYsfpGqq90TXKZzdX WG91zvFjKJbvLo+SP8b0lQuSQizgXe030bpZhk4NSoQSum5M3BSh58KvS//bWDAt S3Mv2frYnJNRBXAHtwn1z/ZM0Wy4nyFDAUHM4+eeCPnR+l9COBZGikiLhQC4oUtC Xb/ghuakC1kSoAPQt+VVUgMBPuyLd64zcDnKsYdUneq8zUgLfBwJV4GzvVSw78jB v7jHBREkmDutyGItli5SojRQPwgPNiq3eOAminXm1KifnU+2KgTzu+XGlBJwtB++ 2ceyrH1fyVlu/zKjnYMoGdiLYaavZGgVHoHBiaPgcrIXYSHK0+c6QGzPXdYGbw3L gCRS3Ci7ppXMUVE0W98UpQg38gpexX7kUXkC/ylIgj7xpf7bZbrtC6d4YJNVCHXt Ev4u0VnGa/JbkZgixQ55nsqQ8RXj6aT9tQLZDV7ohe3vI8Ya7hX6PwoGf8CMDPgg e3naYEKtiehoKeX+izFXAoqPyV7ChtKpzmRgAuYruuMp7c60a4ShSBexuutskUUX FgvEATJ7+HOyqrTLKBlOErQe/rttCem3tZcTV/5iTVC3G+5PlHQbQSFreAwwGhlj qVyh4OgKLldHyXOApqDACUyrgZKzDw6XWEgdi3wo5Rzr5SQOQ+o= =O5+H -----END PGP SIGNATURE----- --u6c734qvleouuetg--