From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Richard M. Stallman" Newsgroups: gmane.emacs.devel Subject: Re: bootstrap problem with union Lisp_Object Date: Sun, 11 Dec 2005 11:49:07 -0500 Message-ID: References: <55DA5764-DDB6-4858-9CE2-065857CDC863@gnu.org> <3AFF0594-F842-4079-9A3B-D1CF7358A281@raeburn.org> <0D268F0D-B278-4307-86E3-E0FCE7A3B57B@raeburn.org> <87pso6anui.fsf-monnier+emacs@gnu.org> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1134322072 18499 80.91.229.2 (11 Dec 2005 17:27:52 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 11 Dec 2005 17:27:52 +0000 (UTC) Cc: schwab@suse.de, raeburn@raeburn.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 11 18:27:43 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1ElUz5-0002GG-CS for ged-emacs-devel@m.gmane.org; Sun, 11 Dec 2005 18:27:39 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ElUzW-0001kk-FB for ged-emacs-devel@m.gmane.org; Sun, 11 Dec 2005 12:28:06 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ElUPG-00005J-3z for emacs-devel@gnu.org; Sun, 11 Dec 2005 11:50:38 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ElUPE-0008Ve-HF for emacs-devel@gnu.org; Sun, 11 Dec 2005 11:50:37 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ElUPD-0008Uv-Gb for emacs-devel@gnu.org; Sun, 11 Dec 2005 11:50:35 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1ElUQn-0002tc-8I for emacs-devel@gnu.org; Sun, 11 Dec 2005 11:52:13 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1ElUNn-0000Sc-BO; Sun, 11 Dec 2005 11:49:07 -0500 Original-To: storm@cua.dk (Kim F. Storm) In-reply-to: (storm@cua.dk) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:47456 Archived-At: May I suggest that you (RMS) add _all_ bugs that you want to be fixed before the release to FOR-RELEASE, and then change the above to: I keep track of bugs, and when nobody works on a bug report for a few weeks, I do put it into FOR-RELEASE. I don't do this immediately. Usually I either ask a specific appropriate person to work on the bug, or I wait a while, since often someone will fix the bug. Or even better, we should make a file etc/KNOWN_BUGS which we can keep up-to-date with known, unresolved bugs. That would be somewhat more work than what I am doing now. I have no objection to maintaining a file admin/KNOWN_BUGS if someone wants to do it. That file should not be part of the release. Who's talking about postponing debugging of known bugs? I'm the only one talking about it, but lots of people appear to be doing it ;-{.