From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: help-guix@gnu.org
Subject: Writing GNU Guix commit messages
Date: Sun, 25 Jul 2021 10:16:34 +0000 [thread overview]
Message-ID: <c54bb524-e8be-735e-583b-adaed89c8c23@posteo.de> (raw)
Hi!
My question is regarding writing of commit messages for sending in patches for
GNU Guix. Previously I tried to simply answer all questions mentioned at
https://www.gnu.org/prep/standards/html_node/Change-Logs.html#Change-Logs
However, it turned out, that that was not the desired format. Now I would like
to make a patch for a new version of a package and I would like to get the
format right this time. I also remember it being mentioned, that there is some
tools distributed with GNU Guix, that is supposed to help with that.
Can you provide links for the documentation of how to get the commit message
right or provide instructions of the necessary steps to take?
Best regards,
Zelphir
--
repositories: https://notabug.org/ZelphirKaltstahl
next reply other threads:[~2021-07-25 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-25 10:16 Zelphir Kaltstahl [this message]
2021-07-25 22:03 ` Writing GNU Guix commit messages Ricardo Wurmus
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=c54bb524-e8be-735e-583b-adaed89c8c23@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=help-guix@gnu.org \
/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).