From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
48592@debbugs.gnu.org, Jonas Bernoulli <jonas@bernoul.li>
Subject: bug#48592: [PATCH 0/2] Support plural forms of Author and Maintainer library headers
Date: Mon, 24 May 2021 14:10:55 +0200 [thread overview]
Message-ID: <87lf84nxgw.fsf@gmx.de> (raw)
In-Reply-To: <914C6F2B-140D-4681-A60E-C844A1DEFF29@gnu.org> (Eli Zaretskii's message of "Mon, 24 May 2021 12:44:48 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Sure adding a note to lm-maintainer technically accomplishes the same,
>> but once one has started using lm-maintainer, then one doesn't
>> periodically go back to see whether a new notes have been added to its
>> doc-string. But something like this would do the trick of guiding the
>> attention towards the extended functionality and its updated
>> documentation:
>>
>> In package-build--desc-from-library:
>> lib/package-build/package-build.el:516:26: Warning: ‘lm-maintainer’ is
>> an
>> obsolete function (as of 28.1); use ‘lm-maintainers’ instead.
>>
>> Yes, there is nothing wrong with ignoring all but the first maintainer
>> (except of course, not properly attributing the contributions of the
>> others as they choose to present it), but it seems to me that having
>> to:
>>
>> - (lm-maintainer)
>> + (car (lm-maintainers))
>>
>> is perfectly acceptable in cases where only "the" maintainer can be
>> mentioned because there is not enough room to display the names of all
>> maintainers. (So it is still a good idea to list the primus inter
>> pares
>> maintainer first.)
>
>
> I think this warning will be a gratuitous annoyance in enough
> legitimate use cases to make the complaints serious. If it's okay to
> take the 'car' of a list, then it should also be okay to call a
> function which does just that. It's not like lm-maintainers returns
> an opaque object.
>
> Again, if the others are fine with the deprecation, I will yield.
Still fine by me, with this obsoletion warning. FWIW.
Best regards, Michael.
next prev parent reply other threads:[~2021-05-24 12:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 20:25 bug#48592: [PATCH 0/2] Support plural forms of Author and Maintainer library headers Jonas Bernoulli
2021-05-22 20:32 ` bug#48592: [PATCH 1/2] " Jonas Bernoulli
2021-05-22 20:32 ` bug#48592: [PATCH 2/2] * lisp/emacs-lisp/lisp-mnt.el (lm-crack-address): Right-trim name Jonas Bernoulli
2021-05-23 6:46 ` bug#48592: [PATCH 0/2] Support plural forms of Author and Maintainer library headers Eli Zaretskii
2021-05-23 8:43 ` Jonas Bernoulli
2021-05-23 9:31 ` Eli Zaretskii
2021-05-23 9:52 ` Colin Baxter
2021-05-23 11:08 ` Lars Ingebrigtsen
2021-05-23 11:48 ` Michael Albinus
2021-05-23 18:21 ` Jonas Bernoulli
2021-05-23 18:45 ` Michael Albinus
2021-05-23 21:14 ` Jonas Bernoulli
2021-05-24 7:04 ` Michael Albinus
2021-05-24 7:28 ` Eli Zaretskii
2021-05-24 8:58 ` Jonas Bernoulli
2021-05-24 9:22 ` Christopher Dimech
2021-05-24 12:16 ` Michael Albinus
2021-05-24 9:44 ` Eli Zaretskii
2021-05-24 12:10 ` Michael Albinus [this message]
2021-05-24 13:51 ` Lars Ingebrigtsen
2021-06-30 17:59 ` Jonas Bernoulli
2021-06-30 19:24 ` Michael Albinus
2021-06-30 19:41 ` Jonas Bernoulli
2021-07-01 11:40 ` Lars Ingebrigtsen
2024-02-14 1:43 ` 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=87lf84nxgw.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=48592@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jonas@bernoul.li \
--cc=larsi@gnus.org \
/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.