unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Please write "Update to <version>" instead of "Update snapshot"
Date: Sun, 26 Nov 2017 23:09:14 +0100	[thread overview]
Message-ID: <871skkvgj9.fsf@gnu.org> (raw)
In-Reply-To: <20171126190315.GB30789@jasmine.lan> (Leo Famulari's message of "Sun, 26 Nov 2017 14:03:15 -0500")

Heya,

Leo Famulari <leo@famulari.name> skribis:

> On Sat, Nov 25, 2017 at 07:43:11PM -0500, Mark H Weaver wrote:
>> In my opinion, the version number is a very useful piece of information
>> to see for update commits when browsing the commit history.  I regard
>> the practice of omitting the version number to be a slowly creeping
>> regression in our otherwise exceptionally good conventions for commit
>> logs.  I humbly propose that we nip this regression in the bud.
>
> I agree that the commit message should always include the new version of
> the package being updated.

I plaid guilty here, but yes, I agree with giving a commit ID in the
summary line when updating the ‘guix’ package and others.

Apologies for the confusion.

Ludo’.

  reply	other threads:[~2017-11-26 22:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-26  0:43 Please write "Update to <version>" instead of "Update snapshot" Mark H Weaver
2017-11-26 19:03 ` Leo Famulari
2017-11-26 22:09   ` Ludovic Courtès [this message]
     [not found] <20171109014628.6934.66587@vcs0.savannah.gnu.org>
     [not found] ` <20171109014630.1CC31201B8@vcs0.savannah.gnu.org>
2017-11-13  4:14   ` 01/01: gnu: totem: Enable parallel build Mark H Weaver
2017-11-13 12:49     ` Kei Kebreau
2017-11-26  1:21       ` Please write "Update to <version>" instead of "Update snapshot" Kei Kebreau

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=871skkvgj9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).