From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: incal@dataswamp.org, emacs-devel@gnu.org
Subject: Re: emacs-lisp-project [was: Re: Custom vtable.el sorters]
Date: Sun, 13 Oct 2024 08:50:23 +0300 [thread overview]
Message-ID: <86wmictuu8.fsf@gnu.org> (raw)
In-Reply-To: <E1szpLD-0002e1-Ls@fencepost.gnu.org> (message from Richard Stallman on Sat, 12 Oct 2024 23:32:23 -0400)
> From: Richard Stallman <rms@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Sat, 12 Oct 2024 23:32:23 -0400
>
> > What one could do, is split emacs-devel into `emacs-devel' and
> > `emacs-project' (or maybe `emacs-lisp-project').
>
> What would be the _topic_ for the second list?
>
> > emacs-project would then be supportive of anyone being active
> > with emacs at their own (any) level,
>
> That proposes an _attitude_ for the list, but it needs to say what topics
> are to be discussed there.
From where I stand, creating yet another mailing list related to Emacs
development is not a good idea, primarily because we will never be
able to separate the issues well enough for such a division to be
effective. The clear disadvantage of this is that there will be
another mailing list to manage, so the advantages need to be very
clear to outweigh that, and they don't in this case.
next prev parent reply other threads:[~2024-10-13 5:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 6:06 Custom vtable.el sorters Kristoffer Balintona
2024-10-03 23:35 ` Adam Porter
2024-10-05 0:44 ` Kristoffer Balintona
2024-10-05 1:37 ` Emanuel Berg
2024-10-05 2:24 ` Adam Porter
2024-10-09 2:04 ` Kristoffer Balintona
2024-10-09 20:06 ` emacs-lisp-project [was: Re: Custom vtable.el sorters] Emanuel Berg
2024-10-13 3:32 ` Richard Stallman
2024-10-13 5:50 ` Eli Zaretskii [this message]
2024-10-13 14:23 ` Philip Kaludercic
2024-10-14 5:44 ` Kristoffer Balintona
2024-10-14 13:57 ` Ship Mints
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=86wmictuu8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=incal@dataswamp.org \
--cc=rms@gnu.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 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).