unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Rostislav Svoboda <rostislav.svoboda@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Liliana Marie Prikler <liliana.prikler@gmail.com>,
	Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
	67272@debbugs.gnu.org, Andrew Tropin <andrew@trop.in>
Subject: [bug#67272] [PATCH] gnu: Add emacs-zop-to-char.
Date: Mon, 20 Nov 2023 10:40:16 +0100	[thread overview]
Message-ID: <CAEtmmexA6Wf5VeEiSKvAAMDSgWu3SjTvqaoA2+LAqjk5ibW0+g@mail.gmail.com> (raw)
In-Reply-To: <871qcknank.fsf@nicolasgoaziou.fr>

Hello

> I disagree. Guix usually sticks to actual releases [...] Note that if the last change was that important for the author, they would have made a release out of it.

Sticking to actual releases makes sense for packages that follow a
"release-has-a-version" policy, which is common for big & popular
ones.

But there's a number [see below] of smaller, less popular elisp
packages with infrequent contributions where the author doesn't really
bother with a strict "tagged-releases" policy. Sometimes it's
forgotten over the years, so "rolling-releases" become the norm.

IMO that's the case for our
https://github.com/thierryvolpiatto/zop-to-char too. Our 00152aa was
done on May 1, 2018. That's over five years ago. Waiting for 1.2
doesn't make sense. It's probably not happening anytime soon, not even
soon-ish, even though the 00152aa seems to be important.

Cheers

Few examples:

| url                                               | github stars |
last commit  | nr of commits | nr of releases |
| https://github.com/007kevin/pdf-view-restore      |           34 |
Sep 4, 2019  |            23 |              1 |
| https://github.com/DamienCassou/json-navigator    |          129 |
Sep 4, 2023  |            43 |              1 |
| https://github.com/FelipeLema/emacs-counsel-gtags |           22 |
Feb 22, 2021 |           208 |              1 |
| https://github.com/Kungi/helm-cider-history       |            2 |
Jul 19, 2015 |             3 |              0 |
| https://github.com/ZehCnaS34/zonokai-emacs        |           11 |
Mar 22, 2016 |           130 |              0 |




  reply	other threads:[~2023-11-20  9:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-19  9:54 [bug#67272] [PATCH] gnu: Add emacs-zop-to-char Rostislav Svoboda
2023-11-19 13:41 ` Liliana Marie Prikler
2023-11-19 13:51   ` Rostislav Svoboda
2023-11-19 16:27     ` Liliana Marie Prikler
2023-11-19 16:28       ` Liliana Marie Prikler
2023-11-20 12:26       ` Rostislav Svoboda
2023-11-20 19:24         ` Liliana Marie Prikler
2023-11-19 18:38 ` Nicolas Goaziou via Guix-patches via
2023-11-19 19:01   ` Rostislav Svoboda
2023-11-20  7:31     ` Nicolas Goaziou via Guix-patches via
2023-11-20  9:40       ` Rostislav Svoboda [this message]
2023-11-20 10:47         ` Nicolas Goaziou via Guix-patches via
2023-11-20 12:28           ` Rostislav Svoboda
2023-11-20 19:38         ` Liliana Marie Prikler
2024-06-19  7:43           ` bug#67272: " 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=CAEtmmexA6Wf5VeEiSKvAAMDSgWu3SjTvqaoA2+LAqjk5ibW0+g@mail.gmail.com \
    --to=rostislav.svoboda@gmail.com \
    --cc=67272@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 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).