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: kfogel@red-bean.com, pwr@skeletons.cc, emacs-devel@gnu.org
Subject: Re: Proposal for an emacs-humanities mailing list
Date: Mon, 30 Nov 2020 18:12:02 +0200	[thread overview]
Message-ID: <83sg8qkenh.fsf@gnu.org> (raw)
In-Reply-To: <87wny34254.fsf@gmx.de> (message from Michael Albinus on Mon, 30 Nov 2020 10:36:39 +0100)

> From: Michael Albinus <michael.albinus@gmx.de>
> Date: Mon, 30 Nov 2020 10:36:39 +0100
> Cc: Karl Fogel <kfogel@red-bean.com>, pwr@skeletons.cc, emacs-devel@gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > However, I don't understand what is expected from the active Emacs
> > developers wrt this list.  It sounds like they will need to subscribe
> > to this new list, for it to be useful?
> 
> I do expect this list to appear on gmane. I, for example, would
> subscribe to that gmane group then, w/o the burden of getting further
> emails. As I do with all Emacs related mailing lists I'm interested in.

I meant the fact of participation, no matter what will be the medium.



  reply	other threads:[~2020-11-30 16:12 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-29  6:57 Proposal for an emacs-humanities mailing list Paul W. Rankin via Emacs development discussions.
2020-11-30  1:24 ` Karl Fogel
2020-11-30  3:16   ` Bob Newell
2020-12-01  5:20     ` Richard Stallman
2020-12-01 10:59     ` 황병희
2020-11-30  3:31   ` Eli Zaretskii
2020-11-30  3:55     ` Paul W. Rankin via Emacs development discussions.
2020-11-30  4:40     ` Karl Fogel
2020-11-30  5:41       ` Eli Zaretskii
2020-11-30  6:03         ` Paul W. Rankin via Emacs development discussions.
2020-11-30 16:02           ` Eli Zaretskii
2020-12-02 14:54             ` Eli Zaretskii
2020-12-03  8:30               ` Paul W. Rankin via Emacs development discussions.
2020-12-03  9:15                 ` Protesilaos Stavrou
2020-12-03 10:35                   ` Paul W. Rankin via Emacs development discussions.
2020-12-12 12:38                   ` Eli Zaretskii
2020-12-14 22:28                     ` Karl Fogel
2020-12-03  9:43                 ` Jean Louis
2020-12-03 10:34                   ` Paul W. Rankin via Emacs development discussions.
2020-12-03 10:16                 ` Joost Kremers
2020-12-04  5:55                   ` Richard Stallman
2020-12-03 20:10                 ` Arthur Miller
2020-12-03 20:48                   ` Stefan Monnier
2020-12-03 21:07                     ` Arthur Miller
2020-12-03 23:22                       ` Stefan Monnier
2020-12-03 23:41                         ` Arthur Miller
2020-11-30 13:39         ` Leo Vivier
2020-11-30 17:23           ` Eric Abrahamsen
2020-11-30 21:27         ` Karl Fogel
2020-11-30 23:17           ` Drew Adams
2020-11-30 23:29             ` Gregory Heytings via Emacs development discussions.
2020-11-30 23:31             ` Karl Fogel
2020-12-01  8:57             ` tomas
2020-12-01 11:43               ` Jean Louis
2020-12-01 16:46               ` Drew Adams
2020-12-01 20:55                 ` tomas
2020-12-01 17:42               ` Eric Abrahamsen
2020-12-02  4:29                 ` Richard Stallman
2020-12-02  6:41                   ` Eric Abrahamsen
2020-12-01  9:17             ` tomas
2020-12-01 11:40           ` Jean Louis
2020-11-30  9:36     ` Michael Albinus
2020-11-30 16:12       ` Eli Zaretskii [this message]
2020-11-30 16:19         ` Corwin Brust
2020-11-30 19:33           ` Jean Louis
2020-11-30  3:53 ` Zhu Zihao
2020-11-30  4:46 ` Richard Stallman
2020-11-30  9:13 ` Lars Ingebrigtsen
2020-11-30 12:03 ` Gregory Heytings via Emacs development discussions.
2020-11-30 13:29   ` Pankaj Jangid
2020-11-30 16:33     ` Eli Zaretskii
2020-11-30 14:36 ` Jean Louis
2020-11-30 16:13   ` Corwin Brust

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=83sg8qkenh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kfogel@red-bean.com \
    --cc=michael.albinus@gmx.de \
    --cc=pwr@skeletons.cc \
    /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.