guix-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#34732] [PATCH 01/31] gnu: mate-common: update to 1.20.0


From: Leo Famulari
Subject: [bug#34732] [PATCH 01/31] gnu: mate-common: update to 1.20.0
Date: Fri, 15 Mar 2019 13:12:05 -0400
User-agent: Mutt/1.11.3 (2019-02-01)

On Mon, Mar 04, 2019 at 12:18:47PM +0100, guy fleury iteriteka wrote:
> ---
>  gnu/packages/mate.scm | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/gnu/packages/mate.scm b/gnu/packages/mate.scm
> index ef94491..57a3ced 100644
> --- a/gnu/packages/mate.scm
> +++ b/gnu/packages/mate.scm
> @@ -73,7 +73,7 @@
>  (define-public mate-common
>    (package
>      (name "mate-common")
> -    (version "1.18.0")
> +    (version "1.20.0")

Thank you for these patches!

I noticed that the commit messages are not complete, however. They are
missing the section that describes the changes made in each file.

For a patch like this, that simply updates the package with no other
changes, you'd write the commit message like this:

------
gnu: mate-common: Update to 1.20.0.

* gnu/packages/mate.scm (mate-common): Update to 1.20.0.
------

If there are other changes, they should be described as well.

I recommend looking at our Git history for examples, or asking here on
or IRC if you need help. Can you send an updated patch series?

Normally, I would fix this sort of issue myself before pushing the
patch, but there are too many patches in this case for me to do it.

By the way, this style of commit logs is called the 'GNU Change Log'
style and is documented here:

https://www.gnu.org/prep/standards/html_node/Change-Logs.html

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]