unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org
Subject: Re: Handling BUGS.
Date: Fri, 22 Mar 2002 12:08:27 -0800	[thread overview]
Message-ID: <E16oVKt-0002vI-00@giblet> (raw)
In-Reply-To: 87elic8k8e.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us

   From: Evan Prodromou <evan@glug.org>
   Date: Fri, 22 Mar 2002 13:40:01 -0600

   HOWEVER, it seems that perhaps maintaining the current bug file format
   (except, of course, splitting up bugs between files) might get one
   "there" faster than hoping for -- or hacking on -- an RFC822 parser.

usable rfc822 parsers have already been written (by at least two people
on this mailing list, probably everyone has one in their personal tool
kit).  the program you posted for html-izing BUGS can be easily refitted
to use one of these parsers.  why don't you do this instead of trying to
convince other people not to do this?  it would be very helpful.

thi

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


  reply	other threads:[~2002-03-22 20:08 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 [this message]
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
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=E16oVKt-0002vI-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).