unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Ahmad Draidi <a.r.draidi@redscript.org>, 64755@debbugs.gnu.org
Cc: Andrew Tropin <andrew@trop.in>
Subject: [bug#64755] [PATCH] gnu: git-modes -> emacs-git-modes.
Date: Fri, 21 Jul 2023 20:27:30 +0200	[thread overview]
Message-ID: <aeb7beabb7ccccafdd40028ac54d46daa6e63f8f.camel@gmail.com> (raw)
In-Reply-To: <b921bab4f546ca8ce5c4a9c1a9a9887343e75fda.1689886157.git.a.r.draidi@redscript.org>

Am Freitag, dem 21.07.2023 um 00:49 +0400 schrieb Ahmad Draidi:
> * gnu/packages/emacs-xyz.scm (emacs-git-modes): New variable.
> (git-modes): Deprecate variable.
> ---
> 
> This makes the package name consistent when installing it through
> 'guix package -i' and a variable name in a system declaration file
> (e.g. /etc/config.scm). It finishes the job in #29582.
> 
> Not sure if the deprecation method I used is optimal, since it brings
> back to life the package name 'git-modes'. However, putting 'emacs-
> git-modes' in 'old-name' causes 'warning: ambiguous package
> specification', as expected.
There is define-deprecated/public, as well as more idiomatic ways of
writing the commit message, i.e. 

gnu: Rename git-modes to emacs-git-modes.

* gnu/packages/emacs-xyz.scm (git-modes): Deprecate and rename to…
(emacs-git-modes): … this.

Cheers




  reply	other threads:[~2023-07-21 18:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 20:49 [bug#64755] [PATCH] gnu: git-modes -> emacs-git-modes Ahmad Draidi via Guix-patches via
2023-07-21 18:27 ` Liliana Marie Prikler [this message]
2023-07-22 10:15   ` Ahmad Draidi via Guix-patches via
2023-07-22 10:35 ` [bug#64755] [PATCH v2] gnu: Rename git-modes to emacs-git-modes Ahmad Draidi 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=aeb7beabb7ccccafdd40028ac54d46daa6e63f8f.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=64755@debbugs.gnu.org \
    --cc=a.r.draidi@redscript.org \
    --cc=andrew@trop.in \
    /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).