unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Sarah Morgensen <iskarian@mgsn.dev>
Cc: 49796-done@debbugs.gnu.org
Subject: bug#49796: [PATCH 1/2] etc/committer: Support custom commit messages.
Date: Wed, 11 Aug 2021 00:20:43 +0200	[thread overview]
Message-ID: <87tujxosas.fsf@gnu.org> (raw)
In-Reply-To: <58ef8300317d11726eb2e9cd3e776485aaa95971.1627764883.git.iskarian@mgsn.dev> (Sarah Morgensen's message of "Sat, 31 Jul 2021 14:00:42 -0700")

Hi Sarah,

Sarah Morgensen <iskarian@mgsn.dev> skribis:

> Allow custom change commit messages by supplying a commit message and
> optionally a changelog message as arguments.
>
> * etc/committer.scm.in (break-string-with-newlines)
> (custom-commit-message): New procedures.
> (main)[change-commit-message*]: New sub-procedure. Use them.
> (main): Use it.
> ---
> Hello Guix,
>
> This allows supplying a commit message and optionally a ChangeLog message as
> arguments to committer.scm, which will be used as the message(s) for changes
> to definitions instead of "Update ..." Both support raw newlines, and if the
> changelog message contains ": ", no extra colon is added to the ChangeLog
> message (this is to support custom definition specifiers).

I’m not Ricardo :-) but the change makes sense to me, so I went ahead
and applied it.

Thank you!

Ludo’.




      parent reply	other threads:[~2021-08-10 22:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31 21:00 [bug#49796] [PATCH 1/2] etc/committer: Support custom commit messages Sarah Morgensen
2021-07-31 21:03 ` [bug#49796] [PATCH 2/2] etc/committer: Pass command-line arguments to main Sarah Morgensen
2021-08-02 18:46 ` [bug#49796] [PATCH 1/2] etc/committer: Support custom commit messages Sarah Morgensen
2021-08-10 22:20 ` Ludovic Courtès [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

  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=87tujxosas.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=49796-done@debbugs.gnu.org \
    --cc=iskarian@mgsn.dev \
    /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).