From: Daniele Nicolodi <email@example.com> To: firstname.lastname@example.org Subject: Re: Ignored bugs Date: Tue, 17 Nov 2020 20:51:37 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <20201117184130.t67oqxhnkw5rwozx@E15-2016.optimum.net> On 17/11/2020 19:41, Boruch Baum wrote: > 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 I haven't investigated further than reading this email, but the fact that you are including what look like debbug numbers suggests that you reported those bugs against Emacs. Org is mostly developed outside Emacs and has an independent release cycle. Emacs syncs irregularly with the latest released version of Org. Bug report affecting the latest release of Org can be submitted to this mailing list. This is also the best way to make them known to the Org developers and maintainer. I don't think anyone here really looks into bugs reported to the Emacs debbugs instance: time is limited and the version of Org distributed with Emacs is very often not the most current one, thus the bug reports may anyhow not be relevant anyhow. I suggest you to try to reproduce these bugs with the latest Org release (or the latest snapshot from Org ELPA) and report on this list if the problems persist, see `org-submit-bug-report'. Please complain with the Emacs maintainers about their handling of the bugs on the Emacs bug tracking system, I don't think it a discussion relevant to this mailing list. Cheers, Dan
next prev parent reply other threads:[~2020-11-17 19:53 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 [this message] 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Ignored bugs' \ /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
Code repositories for project(s) associated with this 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).