From: Adam Porter <adam@alphapapa.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50166@debbugs.gnu.org
Subject: bug#50166: 28.0.50; ECM for possible process-status/sentinel bug
Date: Sun, 22 Aug 2021 17:01:01 -0500 [thread overview]
Message-ID: <CAO_b3FX7nj7-Nu6F-44C3zgqknv9925wWbgyn+8y8v6jstavEA@mail.gmail.com> (raw)
In-Reply-To: <871r6lxjjt.fsf@gnus.org>
On Sun, Aug 22, 2021 at 4:21 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> Adam Porter <adam@alphapapa.net> writes:
>
> > The attached file provides an ECM for a possible bug in Emacs's process
> > handling.
>
> What does "ECM" stand for?
According to https://orgmode.org/worg/org-faq.html#ecm:
This is a French acronym used by some mailing list members; it stands
for "Exemple Complet Minimal", or "Complete Minimal Example". The
term refers to test files that can reliably reproduce a bug with the
minimal amount of code. When you report a bug to the mailing list, you
should provide a minimal .org file (with no more text than necessary)
that demonstrates the bug. See this post for more information.
I learned the term from working on Org, and since Org is part of
Emacs, I assumed it was generally familiar to Emacs maintainers as
well. My mistake. :)
next prev parent reply other threads:[~2021-08-22 22:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 20:08 bug#50166: 28.0.50; ECM for possible process-status/sentinel bug Adam Porter
2021-08-22 21:21 ` Lars Ingebrigtsen
2021-08-22 22:01 ` Adam Porter [this message]
2021-08-22 22:18 ` Lars Ingebrigtsen
2021-08-22 22:34 ` Lars Ingebrigtsen
2021-08-22 22:40 ` Lars Ingebrigtsen
2021-08-23 1:31 ` Adam Porter
2021-08-23 1:47 ` Lars Ingebrigtsen
2021-08-23 12:44 ` Lars Ingebrigtsen
2021-08-23 14:06 ` Lars Ingebrigtsen
2021-09-22 20:41 ` Lars Ingebrigtsen
2021-09-25 12:14 ` Adam Porter
2021-09-26 5:31 ` Lars Ingebrigtsen
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=CAO_b3FX7nj7-Nu6F-44C3zgqknv9925wWbgyn+8y8v6jstavEA@mail.gmail.com \
--to=adam@alphapapa.net \
--cc=50166@debbugs.gnu.org \
--cc=larsi@gnus.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 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.