[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' s
From: |
Eli Zaretskii |
Subject: |
bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade' |
Date: |
Wed, 12 Apr 2023 16:28:56 +0300 |
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Dmitry Gutov <dmitry@gutov.dev>, Adam Porter <adam@alphapapa.net>, Eli
> Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>,
> 62750@debbugs.gnu.org
> Date: Wed, 12 Apr 2023 09:22:03 -0400
>
> >> It's annoyingly late to rename, but if we rename without compatibility
> >> aliases (which seems to be an option since these are new in Emacs-29),
> >> then I'd be in favor.
> >
> > What are compatibility aliases? I must have missed something?
>
> I thought we'd rename `package-update` to `package-upgrade` by adding
> the new name and marking the old name as an obsolete alias (a
> "compatibility alias").
>
> I hadn't realized that `package-update` hasn't been in a release yet, so
> we don't need such a compatibility alias.
Even though these commands were available under those names for the
last year or so?
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Adam Porter, 2023/04/10
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Eli Zaretskii, 2023/04/10
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Philip Kaludercic, 2023/04/10
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Stefan Monnier, 2023/04/10
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Dmitry Gutov, 2023/04/11
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Stefan Monnier, 2023/04/11
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Philip Kaludercic, 2023/04/12
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Stefan Monnier, 2023/04/12
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade',
Eli Zaretskii <=
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Stefan Monnier, 2023/04/12
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Dmitry Gutov, 2023/04/14
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Dmitry Gutov, 2023/04/23
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Eli Zaretskii, 2023/04/24
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Adam Porter, 2023/04/24
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Dmitry Gutov, 2023/04/24
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Eli Zaretskii, 2023/04/24
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Dmitry Gutov, 2023/04/24
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Stefan Monnier, 2023/04/30
- bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade', Philip Kaludercic, 2023/04/12