From: Ricardo Wurmus <rekado@elephly.net>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: Writing GNU Guix commit messages
Date: Mon, 26 Jul 2021 00:03:27 +0200 [thread overview]
Message-ID: <87im0y2gr4.fsf@elephly.net> (raw)
In-Reply-To: <c54bb524-e8be-735e-583b-adaed89c8c23@posteo.de>
Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> writes:
> I also remember it being mentioned, that there is some
> tools distributed with GNU Guix, that is supposed to help with
> that.
If you use Emacs and Magit you can use the “update” or “add”
snippets with Yasnippet, i.e. within the commit message window
opened by magit just type “add” and hit TAB to expand the snippet.
You can also use etc/committer.scm, which is part of the source
checkout. It was written to help with mass-upgrades of CRAN
packages; it will not do the right thing in all cases. Notably,
it has some problems separating consecutive package additions.
--
Ricardo
next prev parent reply other threads:[~2021-07-25 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-25 10:16 Writing GNU Guix commit messages Zelphir Kaltstahl
2021-07-25 22:03 ` Ricardo Wurmus [this message]
2021-07-27 8:23 ` Zelphir Kaltstahl
2021-07-27 12:48 ` Efraim Flashner
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87im0y2gr4.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).