From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([209.51.188.92]:53166)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gwZgx-00055L-6V
	for guix-patches@gnu.org; Wed, 20 Feb 2019 16:46:11 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gwZgv-0003jK-6h
	for guix-patches@gnu.org; Wed, 20 Feb 2019 16:46:09 -0500
Received: from debbugs.gnu.org ([209.51.188.43]:57924)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1gwZgp-0003Vf-8g
	for guix-patches@gnu.org; Wed, 20 Feb 2019 16:46:05 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gwZgp-0006d8-6B
	for guix-patches@gnu.org; Wed, 20 Feb 2019 16:46:03 -0500
Subject: [bug#34595] [PATCH] gnu: Add emacs-shroud
Resent-Message-ID: <handler.34595.D34595.155069912523013@debbugs.gnu.org>
References: <87o976p4z3.fsf@disroot.org> <874l8y5ehq.fsf@elephly.net>
From: Brett Gilio <brettg@posteo.net>
In-reply-to: <874l8y5ehq.fsf@elephly.net>
Date: Wed, 20 Feb 2019 15:44:32 -0600
Message-ID: <87ftsi2kzj.fsf@posteo.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
List-Id: <guix-patches.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-patches>,
	<mailto:guix-patches-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-patches/>
List-Post: <mailto:guix-patches@gnu.org>
List-Help: <mailto:guix-patches-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-patches>,
	<mailto:guix-patches-request@gnu.org?subject=subscribe>
Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org
Sender: "Guix-patches" <guix-patches-bounces+kyle=kyleam.com@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 34595-done@debbugs.gnu.org, 34364@debbugs.gnu.org


Ricardo Wurmus writes:

>
> A version string must be monotonically increasing over time.  Commit
> hashes don=E2=80=99t do that, so we use (git-version last-release revision
> commit) instead.
>
> We prefer releases over arbitrary commits.  Since you are the developer,
> could you please tell us what the difference is between this version and
> the previous release?  Could you make a new release instead?

To the OP, there are several packages that use this form. You can look
at some and pretty much directly copy their content and fill in your
relevant information.