emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Daniele Nicolodi <daniele@grinta.net>, emacs-orgmode@gnu.org
Subject: Re: Ignored bugs
Date: Wed, 18 Nov 2020 09:03:50 +0300	[thread overview]
Message-ID: <X7S5RqfUjVhXtWmC@protected.rcdrun.com> (raw)
In-Reply-To: <m2lfezqsxk.fsf@codeisgreat.org>

* Pankaj Jangid <pankaj@codeisgreat.org> [2020-11-18 05:51]:
> Daniele Nicolodi <daniele@grinta.net> writes:
> > 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.
> I was completely unaware of this. I also used to report bugs via emacs'
> report-emacs-bug fascility.
> Moreover, I am building emacs from `master' everyday and assuming
> everything is latest on this. If Org is a different beast then probably
> we should do two things:
> 1. Remove Org from built-in packages and distribute only via ELPA

No, please that would be detrimental. Please note how many users use
Org who do not have Internet or possibility to update Org. Don't
forget that Emacs run on multi user computers.

Please see example here of who is using Debian GNU/Linux:

I hope you may see many educational institutions and understand that
not every computer may be connected to Internet but many will be used
by multiple users.

> 2. And have a completely separate infrastructure for development,
> mailing-lists, bug reports. This we already have. But we should follow
> convention so that it is easier for user to report-org-bugs.

As long as M-x report-emacs-bug is watched out for Org mode and
handled properly and users nicely and considerately transitioned to
Org mailing list (warmly welcomed), there is no serious problem

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

Those who do not have time, do not have.

There are those who do have time and who will help users.

  parent reply	other threads:[~2020-11-18  6:04 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 [this message]
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=X7S5RqfUjVhXtWmC@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=daniele@grinta.net \
    --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).