emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daniele Nicolodi <daniele@grinta.net>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Ignored bugs
Date: Tue, 17 Nov 2020 21:27:53 +0100	[thread overview]
Message-ID: <6e794a47-b58f-df7a-7420-e0c74174ac16@grinta.net> (raw)
In-Reply-To: <20201117201554.y5pz2blxiklq673m@E15-2016.optimum.net>

On 17/11/2020 21:15, Boruch Baum wrote:
> 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...

The page that introduces the Emacs bug tracker already reports that this
mailing list is the right place where to report Org bugs (or feature
request, as is the case for at least one of the bug you reported), and
not the Emacs bug tracker.

I went and read the exchange on bug #42484 and already Bastien told you
that this mailing list is the right place where to report bugs and
submit patches.

You are deliberately ignoring these instructions. What do you expect?

Would you like to elaborate on why making it easy for you to contribute
something to org-mode that solves your problems should be of concerns to
the people of this list, especialy if this comes at extra cost to them?


  reply	other threads:[~2020-11-17 20:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17 18:41 Boruch Baum
2020-11-17 19:51 ` Daniele Nicolodi
2020-11-17 20:15   ` Boruch Baum
2020-11-17 20:27     ` Daniele Nicolodi [this message]
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:

  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=6e794a47-b58f-df7a-7420-e0c74174ac16@grinta.net \
    --to=daniele@grinta.net \
    --cc=boruch_baum@gmx.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: Ignored bugs' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).