From: Michael Albinus <michael.albinus@gmx.de>
To: Toon Claes <toon@iotcl.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, Fermin <fmfs@posteo.net>,
Ted Zlatanov <tzz@lifelogs.com>,
emacs-devel@gnu.org
Subject: Re: Proposal for emacs-emba mailing list
Date: Wed, 30 Dec 2020 11:55:57 +0100 [thread overview]
Message-ID: <8735zn8sw2.fsf@gmx.de> (raw)
In-Reply-To: <874kk34mp3.fsf@iotcl.com> (Toon Claes's message of "Wed, 30 Dec 2020 11:23:20 +0100")
Toon Claes <toon@iotcl.com> writes:
> Also, at the moment we have opened a few issues on the issue tracker on
> EMBA itself [1]. I actually like this, because I think it's easy to
> navigate and categorize and whatnot. But maybe we should also use
> debbugs for this instead?
>
> I just want to avoid having all the history scattered around and not
> able to find things ever again.
Yes, that's something I have thought about as well. But w/o further
policies, we won't find emba infrastructure related bugs easily in the
stream of all Emacs bugs on debbugs.
Best regards, Michael.
prev parent reply other threads:[~2020-12-30 10:55 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 ` Proposal for emacs-build-automation mailing list (was: Proposal for emacs-emba mailing list) Michael Albinus
2020-12-30 10:23 ` Proposal for emacs-emba mailing list Toon Claes
2020-12-30 10:55 ` Michael Albinus [this message]
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=8735zn8sw2.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 \
--cc=tzz@lifelogs.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).