unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Lars Ingebrigtsen <larsi@gnus.org>,  Fermin <fmfs@posteo.net>,
	 Toon Claes <toon@iotcl.com>,
	 emacs-devel@gnu.org
Subject: Proposal for emacs-build-automation mailing list (was: Proposal for emacs-emba mailing list)
Date: Sat, 09 Jan 2021 20:11:37 +0100	[thread overview]
Message-ID: <87eeiu6i3a.fsf_-_@gmx.de> (raw)
In-Reply-To: <lfdfy5nk.fsf_-_@lifelogs.com> (Ted Zlatanov's message of "Wed, 30 Dec 2020 10:01:03 +0000")

Ted Zlatanov <tzz@lifelogs.com> writes:

Hi,

> MA> I'm OK with either name. However, in the latter case we might ask Glenn
> MA> Morris whether he wants to participate. He's the guy running Emacs CI
> MA> tests on hydra.nixos.org.
>
> I'm also in favor of emacs-build-automation with Glenn and other people
> interested, over a specialized emacs-emba mailing list.

Well, somehow we didn't came to a conclusion, and now we have an
emacs-emba mailing list. Since I still believe that
emacs-build-automation is a better name, I propose we correct this
(deleting emacs-emba ML, creating emacs-build-automation ML).

What do people think? I propose, if there is no objection in a couple of
days, we shall go this way.

> Ted

Best regards, Michael.



  reply	other threads:[~2021-01-09 19:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 15:11 Proposal for emacs-emba mailing list Toon Claes
2020-12-29 15:20 ` Michael Albinus
2021-01-18 15:35   ` Ted Zlatanov
2020-12-29 15:48 ` Amin Bandali
2020-12-30  2:48 ` Lars Ingebrigtsen
2020-12-30  4:57   ` Pankaj Jangid
2020-12-30  9:16     ` Michael Albinus
2020-12-30 10:01   ` Ted Zlatanov
2021-01-09 19:11     ` Michael Albinus [this message]
2020-12-30 10:23   ` Toon Claes
2020-12-30 10:55     ` Michael Albinus

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=87eeiu6i3a.fsf_-_@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=fmfs@posteo.net \
    --cc=larsi@gnus.org \
    --cc=toon@iotcl.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).