all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "J.P." <jp@neverwas.me>
Cc: emacs-erc@gnu.org, Amin Bandali <bandali@gnu.org>, 68660@debbugs.gnu.org
Subject: bug#68660: 29.2; ELPA: Wrong type argument w. multiple maintainers in package-menu-mode
Date: Wed, 31 Jan 2024 14:24:05 -0500	[thread overview]
Message-ID: <jwvr0hxtinl.fsf-monnier+emacs__14794.6565340803$1706729188$gmane$org@gnu.org> (raw)
In-Reply-To: <877cjyaa31.fsf@neverwas.me> (J. P.'s message of "Wed, 24 Jan 2024 09:57:06 -0800")

> Yes, what you describe definitely seems preferable. So, I guess
> `:maintainer' (singular) will always be populated no matter what, for
> the benefit of legacy clients who only speak the one. And newer clients
> will be taught to always first check `:maintainers' (plural).

I'd rather have only one of the two (either `:maintainer` or
`:maintainers`) but not both at the same time.  The downside for those
few multi-maintainer packages is fairly small (its only impact is that
`describe-package` will not show the maintainers, which is what we've
had for many years).

> Please let me know if anything is required from ERC to make this a
> reality. And, of course, I very much appreciate your taking the time.

Nothing specific on ERC's side, no.
But patches for `elpa-admin.el` and for Emacs would be welcome (tho
extra time would be welcome as well :-)


        Stefan






  parent reply	other threads:[~2024-01-31 19:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 14:56 bug#68660: 29.2; ELPA: Wrong type argument w. multiple maintainers in package-menu-mode J.P.
2024-01-22 15:23 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found] ` <jwvjzo11jh2.fsf-monnier+emacs@gnu.org>
2024-01-23 14:57   ` J.P.
     [not found]   ` <87o7dcm718.fsf@neverwas.me>
2024-01-23 19:48     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]     ` <jwvplxrx2be.fsf-monnier+emacs@gnu.org>
2024-01-23 22:34       ` J.P.
     [not found]       ` <87le8fisqg.fsf@neverwas.me>
2024-01-24  0:55         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]         ` <jwvv87jsgfz.fsf-monnier+emacs@gnu.org>
2024-01-24  1:22           ` J.P.
     [not found]           ` <87ede7frtz.fsf@neverwas.me>
2024-01-24 14:31             ` J.P.
     [not found]             ` <87y1ceby5w.fsf@neverwas.me>
2024-01-24 15:41               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]               ` <jwv5xziyc60.fsf-monnier+emacs@gnu.org>
2024-01-24 17:57                 ` J.P.
     [not found]                 ` <877cjyaa31.fsf@neverwas.me>
2024-01-27 20:30                   ` Amin Bandali
2024-01-31 19:24                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
     [not found]                   ` <jwvr0hxtinl.fsf-monnier+emacs@gnu.org>
2024-02-01  2:52                     ` J.P.
     [not found]                     ` <87ttmssxok.fsf@neverwas.me>
2024-02-14  1:58                       ` J.P.
     [not found]                       ` <87eddfg61t.fsf@neverwas.me>
2024-02-14 16:59                         ` Philip Kaludercic
     [not found]                         ` <87a5o3gexk.fsf@posteo.net>
2024-02-14 19:15                           ` J.P.
     [not found]                           ` <877cj6eu2t.fsf@neverwas.me>
2024-02-14 20:08                             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]                             ` <jwvmss2lsgn.fsf-monnier+emacs@gnu.org>
2024-02-14 20:54                               ` J.P.

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='jwvr0hxtinl.fsf-monnier+emacs__14794.6565340803$1706729188$gmane$org@gnu.org' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=68660@debbugs.gnu.org \
    --cc=bandali@gnu.org \
    --cc=emacs-erc@gnu.org \
    --cc=jp@neverwas.me \
    --cc=monnier@iro.umontreal.ca \
    /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.