From: Amin Bandali <bandali@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Jim Porter <jporterbugs@gmail.com>,
65245@debbugs.gnu.org, "F. Jason Park" <jp@neverwas.me>,
emacs@unbit.co.uk, Michael Albinus <michael.albinus@gmx.de>,
Eli Zaretskii <eliz@gnu.org>
Subject: bug#65245: Possible code removal in eshell/diff (em-unix.el)
Date: Fri, 18 Aug 2023 00:33:15 -0400 [thread overview]
Message-ID: <878ra99dh0.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkSMLKw5B1b5x_FoCrhoLdfNnUKBAPwg4C8XqxOm5uveQ@mail.gmail.com>
Hi Stefan, all,
Stefan Kangas writes:
> [Copying in Amin Bandali.]
>
> Michael Albinus <michael.albinus@gmx.de> writes:
>
>> According to admin/MAINTAINERS, Amin Bandali is the official eshell
>> maintainer. Could we please fix this?
>
> Perhaps that should also be moved "Maintainer:" headers in
> eshell/*.el. It would presumably make the information easier to find
> for hapless developers.
Regarding eshell, I never assumed its maintenance; rather, I'd added
myself to the second section of admin/MAINTAINERS, indicating that I'd
be willing to try maintaining it if no one else does. But it appears
that things changed recently, with Jim stepping up to maintain it per
046b5eb90d2a (thanks Jim!).
> BTW, I see some conflicting information for ERC in admin/maintainers
> and lisp/erc.el. The former lists Kelvin White, while the latter
> lists Amin Bandali and F. Jason Park.
>
Regarding ERC, lisp/erc/erc.el is the current and correct one:
F. Jason Park (J.P.) and I are its co-maintainers. As far as I can
tell, neither Kelvin White nor Vibhav Pant have made any commits to
lisp/erc/ in years.
Thanks,
-a
next prev parent reply other threads:[~2023-08-18 4:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 10:49 bug#65245: Possible code removal in eshell/diff (em-unix.el) Richard Hopkins
2023-08-13 13:18 ` Stefan Kangas
2023-08-13 13:33 ` Eli Zaretskii
2023-08-13 16:49 ` Stefan Kangas
2023-08-13 17:32 ` Jim Porter
2023-08-13 17:54 ` Eli Zaretskii
2023-08-14 7:26 ` Michael Albinus
2023-08-14 9:07 ` Stefan Kangas
2023-08-18 4:33 ` Amin Bandali [this message]
2023-08-19 10:54 ` Stefan Kangas
2023-08-14 12:04 ` Eli Zaretskii
2023-08-15 3:02 ` Jim Porter
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878ra99dh0.fsf@gnu.org \
--to=bandali@gnu.org \
--cc=65245@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=emacs@unbit.co.uk \
--cc=jp@neverwas.me \
--cc=jporterbugs@gmail.com \
--cc=michael.albinus@gmx.de \
--cc=stefankangas@gmail.com \
/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/emacs.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).