unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: ttn@glug.org, evan@glug.org, guile-devel@gnu.org
Subject: Re: Handling BUGS.
Date: 24 Mar 2002 23:00:10 +0100	[thread overview]
Message-ID: <87hen5zkwl.fsf@zagadka.ping.de> (raw)
In-Reply-To: <874rj54ql4.fsf@raven.i.defaultvalue.org>

Rob Browning <rlb@defaultvalue.org> writes:

> On second thought, I completely agree that just having one set of
> files is a better idea, though if the bugs database keeps growing, we
> might need to archive older stuff at some point -- that's all I was
> really thinking of.  However there are probably much better ways to
> handle that.

When we have a mass of bugs in the data base, we'll probably also have
good tools to browse them.  Just looking at them with 'ls' wont scale,
but we don't need to do that.

> However I *am* a little hesitant about the free-form bug/file-names,
> but since I'm having trouble figuring out exactly why that worries
> me, we'll just ignore me for now :>

What worries me slightly is that in a listing like

    README
    autoconf-woes
    autoconf-woes-2
    bug-0
    bug-1
    bug-2
    no-bugs-database
    ...

it might not be apparent that all files describe bugs, not just the
"bug-*" ones.

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-03-24 22:00 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 [this message]
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=87hen5zkwl.fsf@zagadka.ping.de \
    --to=mvo@zagadka.ping.de \
    --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).