all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@infotropique.org>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 28020-done@debbugs.gnu.org
Subject: [bug#28020] [PATCH] gnu: Add emacs-gitpatch.
Date: Fri, 11 Aug 2017 06:56:46 +0000	[thread overview]
Message-ID: <20170811065646.26egherqrbecpend@abyayala> (raw)
In-Reply-To: <4c62b87d.AEQAOV3jPRsAAAAAAAAAAAPU2QkAAAACwQwAAAAAAAW9WABZjJhx@mailjet.com>

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]

Arun Isaac transcribed 0.7K bytes:
> 
> > 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?

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.
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2017-08-11  6:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08 18:02 [bug#28020] [PATCH] gnu: Add emacs-gitpatch Oleg Pykhalov
2017-08-10  9:12 ` bug#28020: " Arun Isaac
2017-08-10 12:06   ` [bug#28020] " ng0
2017-08-10 16:26     ` Arun Isaac
2017-08-10 16:35       ` Tobias Geerinckx-Rice
2017-08-10 16:39         ` Arun Isaac
     [not found]     ` <a0b9df8d.AEEAOmPO1j4AAAAAAAAAAAPU2QkAAAACwQwAAAAAAAW9WABZjIlJ@mailjet.com>
2017-08-10 16:55       ` ng0
2017-08-10 17:31         ` Arun Isaac
     [not found]         ` <9b857f17.AEQAOV3jPRoAAAAAAAAAAAPU5Q8AAAACwQwAAAAAAAW9WABZjJhx@mailjet.com>
2017-08-11  0:25           ` Tobias Geerinckx-Rice
2017-08-11  6:48             ` Arun Isaac
2017-08-11  8:55               ` continued discussion on git commit messages ng0
     [not found]         ` <4c62b87d.AEQAOV3jPRsAAAAAAAAAAAPU2QkAAAACwQwAAAAAAAW9WABZjJhx@mailjet.com>
2017-08-11  6:56           ` ng0 [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=20170811065646.26egherqrbecpend@abyayala \
    --to=ng0@infotropique.org \
    --cc=28020-done@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    /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.