all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs@unbit.co.uk, jporterbugs@gmail.com, stefankangas@gmail.com,
	65245@debbugs.gnu.org
Subject: bug#65245: Possible code removal in eshell/diff (em-unix.el)
Date: Mon, 14 Aug 2023 15:04:20 +0300	[thread overview]
Message-ID: <83il9hbzjv.fsf@gnu.org> (raw)
In-Reply-To: <87o7ja2igg.fsf@gmx.de> (message from Michael Albinus on Mon, 14 Aug 2023 09:26:07 +0200)

> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Jim Porter <jporterbugs@gmail.com>,  emacs@unbit.co.uk,
>   65245@debbugs.gnu.org,  stefankangas@gmail.com
> Date: Mon, 14 Aug 2023 09:26:07 +0200
> 
> > Changes in any Emacs package that has an active maintainer should be
> > coordinated with that maintainer.  The only exceptions are obvious
> > fixes like typos, clear omissions, and other such stuff.
> 
> According to admin/MAINTAINERS, Amin Bandali is the official eshell
> maintainer. Could we please fix this?

Jim, care to add yourself to that file?

(Btw, I never consult that file.  I always look at "git log" instead.)





  parent reply	other threads:[~2023-08-14 12:04 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
2023-08-19 10:54                 ` Stefan Kangas
2023-08-14 12:04             ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83il9hbzjv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65245@debbugs.gnu.org \
    --cc=emacs@unbit.co.uk \
    --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 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.