From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.lisp.guile.devel Subject: Re: Handling BUGS. Date: Thu, 21 Mar 2002 22:35:11 -0800 Sender: guile-devel-admin@gnu.org Message-ID: References: <87g02t4zgn.fsf@raven.i.defaultvalue.org> Reply-To: ttn@glug.org NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1016779170 27099 127.0.0.1 (22 Mar 2002 06:39:30 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 22 Mar 2002 06:39:30 +0000 (UTC) Cc: guile-devel@gnu.org Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16oIi1-00072y-00 for ; Fri, 22 Mar 2002 07:39:29 +0100 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16oIhp-0008D4-00; Fri, 22 Mar 2002 01:39:17 -0500 Original-Received: from ca-crlsbd-u3-c5c-122.crlsca.adelphia.net ([68.64.59.122] helo=giblet) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16oIgP-0008BZ-00 for ; Fri, 22 Mar 2002 01:37:49 -0500 Original-Received: from ttn by giblet with local (Exim 3.33 #1 (Debian)) id 16oIdr-00027n-00; Thu, 21 Mar 2002 22:35:11 -0800 Original-To: rlb@defaultvalue.org In-Reply-To: <87g02t4zgn.fsf@raven.i.defaultvalue.org> (message from Rob Browning on Thu, 21 Mar 2002 11:12:24 -0600) Errors-To: guile-devel-admin@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Developers list for Guile, the GNU extensibility library List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.devel:147 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:147 From: Rob Browning Date: Thu, 21 Mar 2002 11:12:24 -0600 (1) create a top level guile CVS module called guile-bugs. (2) create a shallow directory tree: guile-bugs/active/ guile-bugs/resolved/ how about promote devel/ out of guile-core/ entirely? it is generally not related to any specific branch. bugs housekeeping is part of the development effort, after all... (3) create a new file in active/ per bug [...] (4) Add an "affects" field might as well specify a known format, how about rfc822? it's time to see how well the elisp translation machinery holds up to rfc822.el (moderately hairy load IMHO). if not, someone will check in rfc822.scm soon i'm sure. thi _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel