From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Jean Louis <bugs@gnu.support>
Cc: emacs-orgmode@gnu.org, Daniele Nicolodi <daniele@grinta.net>
Subject: Re: Ignored bugs
Date: Wed, 18 Nov 2020 12:20:17 +0530 [thread overview]
Message-ID: <m2eekr5fbq.fsf@codeisgreat.org> (raw)
In-Reply-To: <X7S5RqfUjVhXtWmC@protected.rcdrun.com> (Jean Louis's message of "Wed, 18 Nov 2020 09:03:50 +0300")
Jean Louis <bugs@gnu.support> writes:
>> 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:
> https://www.debian.org/users/
>
> 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.
I completely agree with you. It is important to ship Org along with
Emacs. I was replying to the thought process that insists that org
cannot follow the emacs process. Which was kind of a setback to me.
>> > 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.
Yes. This one. Like it.
next prev parent reply other threads:[~2020-11-18 6:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 18:41 Ignored bugs 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 [this message]
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=m2eekr5fbq.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=bugs@gnu.support \
--cc=daniele@grinta.net \
--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).