From: zimoun <zimon.toutoune@gmail.com>
To: Brett Gilio <brettg@gnu.org>
Cc: timhowes@lavabit.com, 44003@debbugs.gnu.org,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: [bug#44003] [PATCH v2] gnu: emacs-julia-mode: Update to 0.4-0.8bfc709.
Date: Mon, 19 Oct 2020 15:42:16 +0200 [thread overview]
Message-ID: <CAJ3okZ28b0-cZyVUTQWhb_+rYdZz4RMKaK=xYgGSbG8GzKn21A@mail.gmail.com> (raw)
In-Reply-To: <87h7qu3r1z.fsf@debian>
Dear,
On Fri, 16 Oct 2020 at 21:33, Brett Gilio <brettg@gnu.org> wrote:
> Using tagged releases is preferred. I would remove the commit
> let-binding and go about it using version numbering.
It is currently the convention and uniformity matters. :-)
But IMHO it is bad practise. Using commit hash enforces
content-addressed, which is obviously not the case with "tags". Tags
are fragile for upstream in-place replacement, for example. For
reference, [1] and BTW all the thread is worth to read. :-)
1: <https://lists.gnu.org/archive/html/guix-devel/2020-05/msg00236.html>
All the best,
simon
prev parent reply other threads:[~2020-10-19 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 7:33 [bug#44003] [PATCH] gnu: emacs-julia-mode: Update to 0.4-0.8ea90c7 Tim Howes via Guix-patches via
2020-10-15 22:03 ` Nicolas Goaziou
2020-10-16 6:36 ` [bug#44003] [PATCH v2] gnu: emacs-julia-mode: Update to 0.4-0.8bfc709 Tim Howes via Guix-patches via
2020-10-16 19:32 ` Brett Gilio
2020-10-17 22:28 ` [bug#44003] [PATCH v3] gnu: emacs-julia-mode: Update to 0.4 Tim Howes via Guix-patches via
2020-11-02 13:46 ` bug#44003: " Ludovic Courtès
2020-10-19 13:42 ` zimoun [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='CAJ3okZ28b0-cZyVUTQWhb_+rYdZz4RMKaK=xYgGSbG8GzKn21A@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=44003@debbugs.gnu.org \
--cc=brettg@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=timhowes@lavabit.com \
/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).