From: Rostislav Svoboda <rostislav.svoboda@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
Andrew Tropin <andrew@trop.in>,
Liliana Marie Prikler <liliana.prikler@gmail.com>,
74137@debbugs.gnu.org
Subject: [bug#74137] [PATCH] gnu: Add emacs-vi-tilde-fringe.
Date: Fri, 1 Nov 2024 15:41:54 +0100 [thread overview]
Message-ID: <CAEtmmexd4Sa-U1c7_tZOin5XDO+Rs34WCZdev=DpXdA5aSPrEg@mail.gmail.com> (raw)
In-Reply-To: <87jzdnkou6.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
Hello Nicolas,
> I think you can use (version "1.0") and ignore revision. There are no
> functionnal differences between the initial 1.0 release and the commit
> you point to.
???
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.
Cheers
Bost
$ git clone https://github.com/syl20bnr/vi-tilde-fringe && cd
vi-tilde-fringe
...
$ git log
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
commit e6e15638e8c45a5e68d0874d5d8c9a46c4f38a54
Author: syl20bnr <sylvain.benner@gmail.com>
Date: Mon Oct 27 22:40:57 2014 -0400
vi-tilde-fringe.el
commit ef3b2c1ff9d5737b873bb49370e869d54e5e70d7
Author: Sylvain Benner <sylvain.benner@gmail.com>
Date: Mon Oct 27 21:36:28 2014 -0400
Initial commit
[-- Attachment #2: Type: text/html, Size: 1658 bytes --]
next prev parent reply other threads:[~2024-11-01 15:56 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 [this message]
2024-11-01 15:02 ` Nicolas Goaziou via Guix-patches via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEtmmexd4Sa-U1c7_tZOin5XDO+Rs34WCZdev=DpXdA5aSPrEg@mail.gmail.com' \
--to=rostislav.svoboda@gmail.com \
--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 \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.