From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49718) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dfrJW-0002O4-Hj for guix-patches@gnu.org; Thu, 10 Aug 2017 13:32:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dfrJS-0005lJ-G0 for guix-patches@gnu.org; Thu, 10 Aug 2017 13:32:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:46047) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dfrJS-0005ko-46 for guix-patches@gnu.org; Thu, 10 Aug 2017 13:32:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dfrJR-0007Pp-Ow for guix-patches@gnu.org; Thu, 10 Aug 2017 13:32:01 -0400 Subject: [bug#28020] [PATCH] gnu: Add emacs-gitpatch. Resent-Message-ID: Message-Id: MIME-Version: 1.0 From: Arun Isaac Date: Thu, 10 Aug 2017 23:01:15 +0530 In-reply-to: <20170810165517.nojmfy7j4busmwao@abyayala> References: <87wp6ekkef.fsf@gmail.com> <4b50a45a.ADkAACnAL5YAAAAAAAAAAAPejtMAAAACwQwAAAAAAAW9WABZjCOA@mailjet.com> <20170810120612.bi33kbdswgtktohr@abyayala> <20170810165517.nojmfy7j4busmwao@abyayala> Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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: ng0 Cc: 28020-done@debbugs.gnu.org > it would be nice to have a checker for this somehow... Yes, something like `guix lint', but for commits. It should become a git hook much like etc/git/pre-push. 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? Also, having a staging branch to which all commits are made would help keep the master branch clean, and free of these mishaps. But, I guess this issue has been raised before, and the creation of such a staging branch has been postponed. =