From: Jim Porter <jporterbugs@gmail.com>
To: Dmitry Gutov <dmitry@gutov.dev>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Philip Kaludercic <philipk@posteo.net>
Cc: Adam Porter <adam@alphapapa.net>, Eli Zaretskii <eliz@gnu.org>,
Lars Ingebrigtsen <larsi@gnus.org>,
62750@debbugs.gnu.org
Subject: bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade'
Date: Wed, 19 Apr 2023 15:23:44 -0700 [thread overview]
Message-ID: <b22d65ce-ffe5-27df-912d-1621cdef8e04@gmail.com> (raw)
In-Reply-To: <cbe0d50b-e137-2183-3109-706dbd306823@gutov.dev>
On 4/11/2023 2:28 PM, Dmitry Gutov wrote:
> These commands use the term 'update'. But package-menu-mark-upgrades,
> which has been in package.el for years, uses the term 'upgrade' in its
> name and its docstring ("all upgradable packages", etc). There are a few
> auxiliary functions which also use that term, but this is the
> public-facing one.
Given this, I think we should rename the functions. If that means adding
obsolete aliases to be polite, that's ok too. (Personally, I don't think
it's necessary, since users tracking the development builds should
expect some minor breakage, but it doesn't hurt to have aliases.)
next prev parent reply other threads:[~2023-04-19 22:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 12:53 bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade' Adam Porter
2023-04-10 13:18 ` Eli Zaretskii
2023-04-10 13:25 ` Philip Kaludercic
2023-04-10 14:31 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-11 21:28 ` Dmitry Gutov
2023-04-11 21:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-12 7:35 ` Philip Kaludercic
2023-04-12 13:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-12 13:28 ` Eli Zaretskii
2023-04-12 13:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-15 1:34 ` Dmitry Gutov
2023-04-23 23:06 ` Dmitry Gutov
2023-04-24 12:02 ` Eli Zaretskii
2023-04-24 17:28 ` Adam Porter
2023-04-24 18:54 ` Dmitry Gutov
2023-04-24 19:13 ` Eli Zaretskii
2023-04-24 19:38 ` Dmitry Gutov
2023-05-01 1:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-01 13:19 ` Dmitry Gutov
2023-04-12 13:44 ` Philip Kaludercic
2023-04-12 14:36 ` João Távora
2023-04-19 22:23 ` Jim Porter [this message]
2023-04-27 23:27 ` Dmitry Gutov
2023-04-28 14:26 ` Philip Kaludercic
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=b22d65ce-ffe5-27df-912d-1621cdef8e04@gmail.com \
--to=jporterbugs@gmail.com \
--cc=62750@debbugs.gnu.org \
--cc=adam@alphapapa.net \
--cc=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
/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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.