all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: jostein@kjonigsen.net
Cc: npostavs@users.sourceforge.net, public@ryanb.org, emacs-devel@gnu.org
Subject: Re: Making font-lock handle long lines better
Date: Tue, 15 May 2018 19:50:28 +0300	[thread overview]
Message-ID: <831seclv6z.fsf@gnu.org> (raw)
In-Reply-To: <1526371726.2837572.1372427096.22315E49@webmail.messagingengine.com> (message from Jostein Kjønigsen on Tue, 15 May 2018 10:08:46 +0200)

> From: Jostein Kjønigsen <jostein@secure.kjonigsen.net>
> Date: Tue, 15 May 2018 10:08:46 +0200
> 
> But if I understand this correctly this is a bug which was filed and debugged in 2013, half a decade ago, with a
> known fix, but the bug is still in the Emacs codebase. 
> 
> Why? Because whoever filed and diagnosed the bug in the first place can't/won't signed copyright
> assignment papers.

That's not my reading of the discussion in that bug.  The copyright
assignment issue is only tangentially related to the bug, it was
mentioned wrt a package shown in the discussion, but that package is
not the solution to the problem.

As the solution to the problem it was proposed to remove support for
omake or disable it by default.  Upon re-reading the discussion, I
didn't perceive any consensus regarding that proposal.  In any case,
deletion of some lines doesn't require any copyright assignment.

> Now that the problem is solved, can't someone else just make the edit, write the patch, and make this terrible
> bug go away? It's a one-line diff after all. We do provide exceptions for such small patches after all.

If there's an agreement to do that, it should be easy.  But I'm not
sure there as an agreement.

> - Are there any systems in place to follow up "solved" bugs which doesn't result in commits?

This is a volunteer project.  Our "system" in place involves a few
motivated individuals, like Noam and a few others, who routinely
review old bug reports.  If you are asking whether we have people
whose assigned job is to do that, then no.

> - Do we know how many such bugs there currently are?

Please define "such bugs".  The bug tracker supports queries, so given
a specification, we could probably provide an answer.

> - And what improvements could we make to Emacs if there was an initiative to get all those issues properly
> closed?

I hope that more people volunteer to take care of bug reports, both
old and new.  Would you like to work on that?

Thanks.



  reply	other threads:[~2018-05-15 16:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 15:44 Making font-lock handle long lines better Ryan B
2017-02-10 15:57 ` joakim
2017-02-10 16:24 ` Eli Zaretskii
2017-02-11 20:10   ` Wilfred Hughes
2017-02-11 20:28     ` Eli Zaretskii
2017-02-11 23:06       ` Anders Lindgren
2018-05-13 19:44         ` Ryan B
2018-05-15  0:05           ` Noam Postavsky
2018-05-15  8:08             ` Jostein Kjønigsen
2018-05-15 16:50               ` Eli Zaretskii [this message]
2018-05-15 18:32                 ` Stefan Monnier
2017-02-11 22:06 ` Ryan B

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=831seclv6z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jostein@kjonigsen.net \
    --cc=npostavs@users.sourceforge.net \
    --cc=public@ryanb.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.