From: Boruch Baum <boruch_baum@gmx.com>
To: Daniele Nicolodi <daniele@grinta.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Ignored bugs
Date: Tue, 17 Nov 2020 15:15:54 -0500 [thread overview]
Message-ID: <20201117201554.y5pz2blxiklq673m@E15-2016.optimum.net> (raw)
In-Reply-To: <7ef0ec5a-276e-ace7-5316-e168373295ec@grinta.net>
On 2020-11-17 20:51, Daniele Nicolodi wrote:
> Please complain with the Emacs maintainers about their handling of the
> bugs on the Emacs bug tracking system,
How do I know it was "their handling" and not "your handling"? It's
unclear from my view of the thread who performed the actions but all the
other actions on that thread were from a fellow called "Bastien" - is he
one of "theirs" or one of "yours" (or both)?
In any event, it should be of concern to people on this list to make
contributing to org-mode as open and hurdle-free as possible instead of
piling on supplemental demands / requirements. As a case study, you
can review the submissions that I referenced and the elisp content there
that seems would have gone lost had I not taken the extra steps of
engaging on this list. Who knows how many other contributions and
contributors you've "lost" this way...
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
next prev parent reply other threads:[~2020-11-17 20:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 18:41 Ignored bugs Boruch Baum
2020-11-17 19:51 ` Daniele Nicolodi
2020-11-17 20:15 ` Boruch Baum [this message]
2020-11-17 20:27 ` Daniele Nicolodi
2020-11-17 20:54 ` Boruch Baum
2020-11-17 21:36 ` Jean Louis
2020-11-17 23:42 ` Tim Cross
2020-11-18 4:04 ` Ihor Radchenko
2020-12-14 6:55 ` Bastien
2020-11-18 2:50 ` Pankaj Jangid
2020-11-18 3:59 ` Tim Cross
2020-11-18 6:44 ` Pankaj Jangid
2020-11-18 6:50 ` Jean Louis
2020-11-18 7:32 ` Tim Cross
2020-11-18 6:03 ` Jean Louis
2020-11-18 6:50 ` Pankaj Jangid
2020-12-14 7:14 ` Bastien
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201117201554.y5pz2blxiklq673m@E15-2016.optimum.net \
--to=boruch_baum@gmx.com \
--cc=daniele@grinta.net \
--cc=emacs-orgmode@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/org-mode.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).