unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Graves via Guix-patches via <guix-patches@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>, 61008@debbugs.gnu.org
Subject: [bug#61008] [PATCH] gnu: emacs-smartparens: Fix package cl deprecation.
Date: Sun, 22 Jan 2023 20:19:50 +0100	[thread overview]
Message-ID: <87lelul6ll.fsf@ngraves.fr> (raw)
In-Reply-To: <87cz76ply1.fsf@nicolasgoaziou.fr>


> AFAIU, we're fixing a mere warning.
Indeed, it's the case for both patches.

> Why do you think it is worth a patch?

I was just curious about the warning and looked for packages trigerring
it in my config, which are the two packages I sent.

Smartparens is regularly updated but doesn't make new releases, I
hesitated upadting it based on a commit, or use this patch.

Origami's original repo hasn't changed in 5 years, but it had a pull
request waiting for it.

Both are quite used, but still trigger the warning since their codebase
age. Their guix users have the warning and might enquire "for nothing
serious". But all-in-all, it is neither urgent nor important, you can
close both patches if you feel it's better without ;)

-- 
Best regards,
Nicolas Graves




  reply	other threads:[~2023-01-22 19:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 16:29 [bug#61008] [PATCH] gnu: emacs-smartparens: Fix package cl deprecation Nicolas Graves via Guix-patches via
2023-01-22 16:34 ` Nicolas Goaziou
2023-01-22 19:19   ` Nicolas Graves via Guix-patches via [this message]
2023-01-22 22:09     ` Nicolas Goaziou
2023-01-24 13:08 ` [bug#61008] [PATCH v2] gnu: emacs-smartparens: Update to 1.11.0-0.7afd647 Nicolas Graves via Guix-patches via
2023-02-07  8:08   ` bug#61008: " Christopher Baines

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=87lelul6ll.fsf@ngraves.fr \
    --to=guix-patches@gnu.org \
    --cc=61008@debbugs.gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --cc=ngraves@ngraves.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).