From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org
Subject: Re: Bug File Format
Date: Sun, 24 Mar 2002 11:11:51 -0800 [thread overview]
Message-ID: <E16pDPC-0006Gd-00@giblet> (raw)
In-Reply-To: 87g02pn89q.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us
From: Evan Prodromou <evan@glug.org>
Date: Sun, 24 Mar 2002 12:13:53 -0600
Wouldn't it be nice to have bugs defined thusly?
(((number . 1)
(title . "Bug 1")
(reported-date . "10/14/1968")
(reported-by . "Evan Prodromou")
(affects . ("1.4" "1.6" "1.8"))
(fixed-date . ("10/14/1968")))
"Blah blah blah.
and blah.")
I'm going ahead with the RFC822 format, anyways, though.
this would be great if the bug "body" data were more constrained.
keeping it easy to add info to the body (by cut/pasting emailed bug
reports, which may contain quotes and other nasty things) is the most
important factor in adoption (C-y is ok, but C-y C-x C-x M-% " RET \ "
RET ! is just make-work, IMHO).
perhaps you can use rfc822 for top-level format, and sexps format for
some of the header values:
Number: 1
...
Reported-Date: (iso "1968-10-14") # or (american "10/14/1968")
Affects: ("1.4" "1.6" "1.8")
certainly internally a nice alist-like data structure could be useful.
if we can get paperwork out of the way, i'd love to see this worked into
an executable module distributed w/ guile, in which case this style of
bugs-database grokking can be embedded into other programs (modulo SMOP
to separate the bugs-specific database schema, to provide "directory of
rfc822 files qua database" functionality, generally).
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-03-24 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-24 18:13 Bug File Format Evan Prodromou
2002-03-24 19:10 ` Marius Vollmer
2002-03-25 4:04 ` Rob Browning
2002-03-24 19:11 ` Thien-Thi Nguyen [this message]
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=E16pDPC-0006Gd-00@giblet \
--to=ttn@giblet.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).