From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Writing GNU Guix commit messages
Date: Tue, 27 Jul 2021 08:23:18 +0000 [thread overview]
Message-ID: <77a8e464-f6dc-45a6-67f7-8ec68e5eff66@posteo.de> (raw)
In-Reply-To: <87im0y2gr4.fsf@elephly.net>
Hi Ricardo!
Thanks for your reply!
I am using Emacs and Magit, but not yet Yasnippet. Is the snippet for Yasnippet
loaded from the source code of Guix automatically? I imagine I have to somehow
add this snippet first, before I can use it. Or perhaps there is some special
yasnippet file, which yasnippet recognizes and then it completes from that?
About etc/committer.scm: I assume, that I would run this using "guile
etc/committer.scm". Is that the correct way to go?
Best regards,
Zelphir
On 7/26/21 12:03 AM, Ricardo Wurmus wrote:
>
> 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.
>
--
repositories: https://notabug.org/ZelphirKaltstahl
next prev parent reply other threads:[~2021-07-27 8:23 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
2021-07-27 8:23 ` Zelphir Kaltstahl [this message]
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=77a8e464-f6dc-45a6-67f7-8ec68e5eff66@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.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.
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).