From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: evan@glug.org, guile-devel@gnu.org
Subject: Re: Handling BUGS.
Date: Fri, 22 Mar 2002 16:53:46 -0800 [thread overview]
Message-ID: <E16oZn0-0003B7-00@giblet> (raw)
In-Reply-To: <87n0x01bci.fsf@raven.i.defaultvalue.org> (message from Rob Browning on Fri, 22 Mar 2002 16:33:49 -0600)
From: Rob Browning <rlb@defaultvalue.org>
Date: Fri, 22 Mar 2002 16:33:49 -0600
Nope. I just wanted to discuss it (in parallel with other things) so
we'd know where we were going. I'm happy (and was hoping) other
people might be willing to work on it.
ok, if no one objects, i will delete devel/ from guile-core/ and move
its contents to sibling cvs module "devel". when Evan posts the BUGS
exploder script (or if i stumble on some emacs keyboard macro, whichever
happens first), we will use that to create devel/bugs/, one bug per file
therein.
when Evan posts the summarization script (to create BUGS for release and
html suitable for web publishing), we can add it to scripts/ (or to
../guile-scripts/ if there are paperwork problems), modify RELEASE to
include instructions on when and how to run that script, and then delete
BUGS from cvs (all branches).
in the meantime, i'll look into adding something to CVSROOT/modules,
and/or modify ANON-CVS w/ instructions on how to check out devel/ in
addition to guile-core/. fyi, i was able to do:
cvs -d :ext:ttn@subversions.gnu.org:/cvsroot/guile co CVSROOT
cd CVSROOT
cvs edit modules
(btw, i agree that all of this is independent of release schedule. as
long as we include some BUGS file w/ relevant info i'm happy. i'm eager
to put this into place quickly, however, because there are several bugs
i'd like to add to the system -- including some that i started to look
into but haven't figured out yet -- and would prefer to just add them in
one place. maybe i should add them to 1.6 BUGS now.)
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-23 0:53 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 17:12 Handling BUGS Rob Browning
2002-03-21 23:09 ` Neil Jerram
2002-03-22 0:54 ` Rob Browning
2002-03-22 9:03 ` Neil Jerram
2002-03-22 6:35 ` Thien-Thi Nguyen
2002-03-22 9:14 ` Neil Jerram
2002-03-22 14:25 ` Rob Browning
2002-03-22 19:32 ` Thien-Thi Nguyen
2002-03-22 17:40 ` Evan Prodromou
2002-03-22 19:13 ` Thien-Thi Nguyen
2002-03-22 19:40 ` Evan Prodromou
2002-03-22 20:08 ` Thien-Thi Nguyen
2002-03-22 20:34 ` Evan Prodromou
2002-03-22 21:41 ` Thien-Thi Nguyen
2002-03-22 22:33 ` Rob Browning
2002-03-23 0:53 ` Thien-Thi Nguyen [this message]
2002-03-23 12:14 ` Marius Vollmer
2002-03-23 14:12 ` Rob Browning
2002-03-23 14:59 ` Rob Browning
2002-03-24 19:14 ` Marius Vollmer
2002-03-23 21:43 ` Thien-Thi Nguyen
2002-03-24 13:37 ` Marius Vollmer
2002-03-24 19:31 ` Thien-Thi Nguyen
2002-03-24 20:40 ` Marius Vollmer
2002-03-24 21:13 ` Rob Browning
2002-03-24 22:00 ` Marius Vollmer
2002-03-25 3:57 ` Rob Browning
2002-03-25 8:32 ` Thien-Thi Nguyen
2002-03-25 21:05 ` Marius Vollmer
2002-03-25 21:34 ` Thien-Thi Nguyen
2002-03-25 22:31 ` Marius Vollmer
2002-03-25 23:22 ` Thien-Thi Nguyen
2002-03-25 23:39 ` Thien-Thi Nguyen
2002-03-22 20:34 ` Thien-Thi Nguyen
2002-03-22 22:31 ` Rob Browning
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.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E16oZn0-0003B7-00@giblet \
--to=ttn@giblet.glug.org \
--cc=evan@glug.org \
--cc=guile-devel@gnu.org \
--cc=ttn@glug.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.
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).