From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: rlb@defaultvalue.org, evan@glug.org, guile-devel@gnu.org
Subject: Re: Handling BUGS.
Date: 25 Mar 2002 22:05:36 +0100 [thread overview]
Message-ID: <87lmcgz7bz.fsf@zagadka.ping.de> (raw)
In-Reply-To: <E16pPtj-0006vZ-00@giblet>
Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
> From: Marius Vollmer <mvo@zagadka.ping.de>
> Date: 24 Mar 2002 21:40:38 +0100
>
> I don't think bugs need numbers, just no-bugs-database should be
> enough.
>
> numbers are symbolic (see comp.lang.lisp thread on packaging). they
> have extra properties that are useful for ordering and concise to
> reference.
Whatever. Let's not unproductively quibble over this. Let's just say
that numbers are OK, too.
> Yes, good point. What about simply saying that the bug file itself
> has no "." in its name, and related files like test scripts do?
>
> i suggest dot dirs in my other mail (using numbers, but i fancy
> N.SHORT-DESC would be the righteous hybrid solution).
A directory can be seen as a related file, as well, I'd say: bug-12.stuff/
I'll mention this as well.
I will just trot along in workbook/bugs even if we don't have complete
consensus yet. I want to use the new mechanism already for better
managing the 1.6 release.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-25 21:05 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
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 [this message]
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=87lmcgz7bz.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=evan@glug.org \
--cc=guile-devel@gnu.org \
--cc=rlb@defaultvalue.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).