From: Boruch Baum <boruch_baum@gmx.com>
To: emacs-orgmode@gnu.org
Subject: Ignored bugs
Date: Tue, 17 Nov 2020 13:41:30 -0500 [thread overview]
Message-ID: <20201117184130.t67oqxhnkw5rwozx@E15-2016.optimum.net> (raw)
A little over a month ago, I submitted several bug reports related to
org-mode, and sor most of them haven't seen any action whatsoever, not
even an indication that they were noticed. In many cases, I provided
either a total solution or a suggested implementation of a solution.
BUG REPORT: 42484
+ This is of particular concern to me because when it was submitted it
was summarily closed AND ANRCHIVED. When I complained, it was unarchived so
that I could provide a solution and patch of my own, but it has since
been archived AGAIN, so I can't submit an updated patch. Further, it
was never removed from the closed state, so it could easily be
overlooked. (Do I need to explicitly complain that this is awful
management behavior?) So, I have an updated patch that I tried to
submit a few minutes ago that was bounced because the thread is in
read-only archived state.
BUG REPORT: 43954
BUG REPORT: 43955
+ code included
BUG REPORT: 44133
+ code included
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
next reply other threads:[~2020-11-17 18:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 18:41 Boruch Baum [this message]
2020-11-17 19:51 ` Ignored bugs Daniele Nicolodi
2020-11-17 20:15 ` Boruch Baum
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=20201117184130.t67oqxhnkw5rwozx@E15-2016.optimum.net \
--to=boruch_baum@gmx.com \
--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).