unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: rlb@defaultvalue.org, evan@glug.org, guile-devel@gnu.org
Subject: Re: Handling BUGS.
Date: Sat, 23 Mar 2002 13:43:29 -0800	[thread overview]
Message-ID: <E16otIP-0004MH-00@giblet> (raw)
In-Reply-To: <87u1r77a7c.fsf@zagadka.ping.de> (message from Marius Vollmer on 23 Mar 2002 13:14:15 +0100)

   From: Marius Vollmer <mvo@zagadka.ping.de>
   Date: 23 Mar 2002 13:14:15 +0100

   What about calling it "workbook" instead of "devel"?

that's fine by me.

   I have a slightly uneasy feeling about splitting BUGS into multiple
   files.  CVS is not very good at moving or renaming files and we
   wouldn't have a centralized log any more.  I don't see any problems
   with just keeping all bugs in one file.

usually a bug, once interned into the system, should not move (and
should not be deleted).  its status and other attributes can change, of
course, but its relationship to the filesystem need not.  this property
is important; new bugs that are duplicates of, or related to, old bugs
need to be able to refer to old bugs (see bug 6, for example).  same
goes for regression tests.

generally, separating database format from presentation format allows
tuning presentation to everyone's individual taste.  i'm hoping Evan's
bugs renderer will have tasty customization hooks, etc.  a particularly
nice feature would be directory slices:

 cd /tmp
 render-bugs --dir-slice resolved .../workplace/bugs/

creates /tmp/resolved/{3,4,5} (symlinks to .../workplace/bugs/{3,4,5})
where 3,4,5 are determined to satisfy the pre-defined "resolved" filter.

then, you can do further render-bugs on /tmp/resolved/ (perhaps
recursing into /tmp/resolved/1.6/, etc).  when you're done, just rm -rf
/tmp/resolved/.

it would also be nice to accept a predicate for ad-hoc slicing:

 render-bugs --dir-slice-predicate ttn \
               '(equal? (bug-assq (quote reporter)) "ttn")'

bug-assq would need to be provided and other similar primitives.  mixing
pre-defined and ad-hoc reporting like this "allows the simple to be easy
and the complex to be possible" (to further promote a popular meme ;-).
for an example of this kind of reporting, see test-suite/guile-test.

thi

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


  parent reply	other threads:[~2002-03-23 21:43 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 [this message]
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=E16otIP-0004MH-00@giblet \
    --to=ttn@giblet.glug.org \
    --cc=evan@glug.org \
    --cc=guile-devel@gnu.org \
    --cc=rlb@defaultvalue.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).