From: Bastien <email@example.com> To: Boruch Baum <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Ignored bugs Date: Mon, 14 Dec 2020 08:14:12 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <20201117184130.t67oqxhnkw5rwozx@E15-2016.optimum.net> (Boruch Baum's message of "Tue, 17 Nov 2020 13:41:30 -0500") Hi Boruch, Boruch Baum <email@example.com> writes: > 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. I'm not convinced this should be in Org's core. I think it could be in https://orgmode.org/worg/org-hacks.html You can send a patch against https://code.orgmode.org/bzg/worg/ or ask for an account on https://code.orgmode.org to be able to write directly to Worg. > BUG REPORT: 43954 Please use report-emacs-bug for bugs only. For such suggestions, please discuss them on this list. > BUG REPORT: 43955 > > + code included It looks like 43955 is a better version of 43954. > BUG REPORT: 44133 > > + code included The patch seems interesting. Can you resend it on this list in a dedicated thread? Also, you need to format it as described here: https://orgmode.org/worg/org-contribute.html Thanks, -- Bastien
prev parent reply other threads:[~2020-12-14 7:15 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 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 [this message]
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 \ --email@example.com \ --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).