From: Nicolas Goaziou via Guix-patches via <guix-patches@gnu.org>
To: Rostislav Svoboda <rostislav.svoboda@gmail.com>
Cc: Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
Liliana Marie Prikler <liliana.prikler@gmail.com>,
74137@debbugs.gnu.org, Andrew Tropin <andrew@trop.in>
Subject: [bug#74137] [PATCH] gnu: Add emacs-vi-tilde-fringe.
Date: Fri, 01 Nov 2024 16:02:53 +0100 [thread overview]
Message-ID: <87ed3vkndu.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAEtmmexd4Sa-U1c7_tZOin5XDO+Rs34WCZdev=DpXdA5aSPrEg@mail.gmail.com> (Rostislav Svoboda's message of "Fri, 1 Nov 2024 15:41:54 +0100")
Rostislav Svoboda <rostislav.svoboda@gmail.com> writes:
> What do you mean by "the initial 1.0 release"? I see no release tag in the
> repository which consists of just 3 commits anyway.
You're pointing to the following commit:
> commit f1597a8d54535bb1d84b442577b2024e6f910308 (HEAD -> master,
> origin/master, origin/HEAD)
> Author: syl20bnr <sylvain.benner@gmail.com>
> Date: Mon Dec 29 21:55:25 2014 -0500
>
> Add MELPA badge
It has no functional difference with the following, which specifies Vi
Tilde Fringe version to 1.0 through it "Version:" keyword:
> commit e6e15638e8c45a5e68d0874d5d8c9a46c4f38a54
> Author: syl20bnr <sylvain.benner@gmail.com>
> Date: Mon Oct 27 22:40:57 2014 -0400
>
> vi-tilde-fringe.el
Therefore, I suggest to keep using the commit you refer to (f1597...),
but mark it as version 1.0 instead of an obscure 1.0-1.f1597a8.
HTH,
next prev parent reply other threads:[~2024-11-01 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 13:59 [bug#74137] [PATCH] gnu: Add emacs-vi-tilde-fringe Rostislav Svoboda
2024-11-01 14:31 ` Nicolas Goaziou via Guix-patches via
2024-11-01 14:41 ` Rostislav Svoboda
2024-11-01 15:02 ` Nicolas Goaziou via Guix-patches via [this message]
2024-11-01 15:51 ` Rostislav Svoboda
2024-11-01 16:05 ` Nicolas Goaziou via Guix-patches via
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=87ed3vkndu.fsf@nicolasgoaziou.fr \
--to=guix-patches@gnu.org \
--cc=74137@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=cox.katherine.e+guix@gmail.com \
--cc=liliana.prikler@gmail.com \
--cc=mail@nicolasgoaziou.fr \
--cc=rostislav.svoboda@gmail.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).