From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ivan Shmakov Newsgroups: gmane.emacs.devel Subject: Re: 4K Bugs Date: Sat, 26 Dec 2015 17:55:55 +0000 Message-ID: <87k2o1xff8.fsf@violet.siamics.net> References: <87mvszdp6b.fsf@gnus.org> <567E4ABA.3080803@online.de> <83vb7lijub.fsf@gnu.org> <567EAECD.2070403@online.de> <83d1tti2xr.fsf@gnu.org> <87twn5mabk.fsf@gnus.org> <838u4hi24m.fsf@gnu.org> <87bn9dm9h3.fsf@gnus.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1451152593 22495 80.91.229.3 (26 Dec 2015 17:56:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 26 Dec 2015 17:56:33 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 26 18:56:25 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aCt4p-0002or-UX for ged-emacs-devel@m.gmane.org; Sat, 26 Dec 2015 18:56:24 +0100 Original-Received: from localhost ([::1]:39420 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aCt4p-0001Xx-9n for ged-emacs-devel@m.gmane.org; Sat, 26 Dec 2015 12:56:23 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60229) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aCt4b-0001Xe-8l for emacs-devel@gnu.org; Sat, 26 Dec 2015 12:56:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aCt4X-0004mO-DS for emacs-devel@gnu.org; Sat, 26 Dec 2015 12:56:09 -0500 Original-Received: from fely.am-1.org ([2a01:4f8:d15:1b86::2]:33402) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aCt4X-0004lO-4J for emacs-devel@gnu.org; Sat, 26 Dec 2015 12:56:05 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=siamics.net; s=a2013295; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:Sender:References:Subject:To:From; bh=yu0Yo4ZlkMR1fO45H67YBEaCIII+IsSdXiJKDYq4MEM=; b=pR3UWr+tnxGs/gKgs6ZaZQ/BTB5N4UTGG+OX3EitVxAeeT0DJPm3B9yy151htRoZaSQH6+gmfq5xJ4knskNtfU8SsEv2OJe81+O9Yst+SAPm5w7MpfJgxqhR6AwWog69BOStoUHN7Ehp9lcFdwVvg8TY++zFTuQfI2QfaJtH81U=; Original-Received: from violet.siamics.net ([2001:470:1f13:1eb::1:1d]) by fely.am-1.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1aCt4V-0004oz-9K for emacs-devel@gnu.org; Sat, 26 Dec 2015 17:56:03 +0000 Original-Received: from localhost ([::1] helo=violet.siamics.net) by violet.siamics.net with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1aCt4O-0001aA-GC for emacs-devel@gnu.org; Sun, 27 Dec 2015 00:55:56 +0700 In-Reply-To: <87bn9dm9h3.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 26 Dec 2015 17:59:52 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] X-Received-From: 2a01:4f8:d15:1b86::2 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:196901 Archived-At: >>>>> Lars Ingebrigtsen writes: >>>>> Eli Zaretskii writes: [=E2=80=A6] >> Closing bug reports tends to annoy their reporters. Not only the reporters; if I=E2=80=99m supportive of a change requested, closing the respective report will hardly make me any happier =E2=80=93 irrespective of who made the request. > It does, but only because they think "closed" means that the report > is disappeared, and "moreinfo" means that we're still thinking about > it. Both of which are wrong. :-) Semantically, =E2=80=9Cclosed=E2=80=9D means that there=E2=80=99s no bug (= any more) =E2=80=93 that is, the recipe given by the reporter does not reproduce the issue, or the reporter is found to be mistaken on the feature=E2=80=99s intended (and documented) behavior. In the latter case, it may still make sense to review, and possibly amend, the documentation, so to reduce the chance of the intended behavior being confused for a =E2=80=9Cbug=E2=80=9D in the future. (Hence, a =E2= =80=9Cmistaken=E2=80=9D bug report may point at an actual bug in the documentation.) When the bug explicitly requests for the change of the behavior, being =E2=80=9Cclosed=E2=80=9D means that either the change was implemente= d, or a similar feature was provided, or that the assumptions the request=E2=80=99s based upon are no longer relevant (say, when the feature request explicitly concerns some facility that was removed from Emacs altogether.) Then, =E2=80=9Cmoreinfo=E2=80=9D means that the report lacks information essential to reproducing the issue (that is: its recipe is incomplete or missing); while =E2=80=9Cwontfix=E2=80=9D means that the maintainer does not consider rectifying the issue (say, implementing the feature request) to be worth the effort. Technically, closed bugs are archived, which mean that they disappear from the =E2=80=9Cdefault=E2=80=9D http://debbugs.gnu.org/ lists= , and also become =E2=80=9Cimmutable=E2=80=9D =E2=80=93 unless explicitly unarch= ived later. [=E2=80=A6] --=20 FSF associate member #7257 http://am-1.org/~ivan/ =E2=80=A6 3013 B6A0= 230E 334A