From: Ricardo Wurmus <rekado@elephly.net>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: 宋文武 <iyzsong@member.fsf.org>, 34959-done@debbugs.gnu.org
Subject: [bug#34959] Acknowledgement ([PATCH] Add Multiple Common Lisp Packages)
Date: Wed, 10 Apr 2019 19:00:00 +0200 [thread overview]
Message-ID: <87ftqpeqy7.fsf@elephly.net> (raw)
In-Reply-To: <87k1g1q5oh.fsf@gmail.com>
Katherine Cox-Buday <cox.katherine.e@gmail.com> writes:
> Do all commits require message bodies?
Yes, for better or worse we adhere to the GNU conventions in commit
messages. Since the format is predictable and can be, in part, derived
from the changes we offer Emacs snippets that can be used to generate
the commit messages more quickly.
If you’re using Emacs and Magit you only need to type “add” or “update”
and hit TAB to have the commit message generated for you.
(If you’re not using Emacs we would welcome snippets for other editors
to make it writing commit messages easier.)
--
Ricardo
next prev parent reply other threads:[~2019-04-10 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 20:14 [bug#34959] [PATCH] Add Multiple Common Lisp Packages Katherine Cox-Buday
[not found] ` <handler.34959.B.155337211019624.ack@debbugs.gnu.org>
2019-03-23 20:41 ` [bug#34959] Acknowledgement ([PATCH] Add Multiple Common Lisp Packages) Katherine Cox-Buday
2019-03-24 10:01 ` Ricardo Wurmus
2019-03-28 17:38 ` Katherine Cox-Buday
2019-03-28 20:43 ` Ricardo Wurmus
2019-03-29 17:15 ` Katherine Cox-Buday
2019-03-29 23:19 ` Katherine Cox-Buday
2019-04-07 6:13 ` bug#34959: " 宋文武
2019-04-10 14:46 ` [bug#34959] " Katherine Cox-Buday
2019-04-10 17:00 ` Ricardo Wurmus [this message]
2019-04-10 17:57 ` Katherine Cox-Buday
2019-04-10 18:19 ` Ricardo Wurmus
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=87ftqpeqy7.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=34959-done@debbugs.gnu.org \
--cc=cox.katherine.e@gmail.com \
--cc=iyzsong@member.fsf.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).