PavoDive <[email protected]> writes: > I started looking at the not-owned bugs in tracker.orgmode.org. Particularly, > I found > [[https://list.orgmode.org/orgmode/CAJcAo8uEmEuZYNOGnrQ0mRrBPVfnjCXQsJGi27B6pW=aqsz...@mail.gmail.com][this > old thread]]. > > I could not reproduce in Org mode version 9.7.11 (release_9.7.11), GNU Emacs > 30.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.33, cairo version > 1.16.0) of 2025-04-16, *and the thread itself shows the bug went away with > commit 07a4a7286 of August 2020*. > > So please inform me of the correct workflow. I'm getting I should reply to > the original message with "owned" and "fixed"/"resolved"/"closed" per the > BARK docs. Which one should I use?
> Please forget the noob question, I rather asked before I increased someone > else's workload. All the questions are allowed :) Looking at that thread, there is https://list.orgmode.org/orgmode/[email protected]/ from Nicolas where he explicitly says that he fixed the bug. This means that the bug report is really closed. It is just that BARK could not auto-detect the closure made by Nicolas. So, you can simply reply with Fixed. Here are two examples how I dealt with similar situations: - https://list.orgmode.org/orgmode/87wly18kjf.fsf@localhost/ - https://list.orgmode.org/orgmode/87ik9tz7w7.fsf@localhost/ For new bug reports, if there is a bug you cannot reproduce, you need to ask the original submitter about more details. Usually, non-reproducible bugs are reported when the bug is caused by some personal customizations. Referring to Feedback section of the manual usually helps creating a good reproducer. I have added this information to the contribute page. https://git.sr.ht/~bzg/worg/commit/81da19bd -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
