unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@glug.org>
Cc: evan@glug.org, guile-devel@gnu.org
Subject: Re: More Bug Stuff
Date: Mon, 25 Mar 2002 17:00:11 -0500	[thread overview]
Message-ID: <E16pcVf-0001rM-00@colo.agora-net.com> (raw)
In-Reply-To: <87hen4z5xf.fsf@zagadka.ping.de> (message from Marius Vollmer on 25 Mar 2002 22:35:56 +0100)

   From: Marius Vollmer <mvo@zagadka.ping.de>
   Date: 25 Mar 2002 22:35:56 +0100

	     N.ext  --  A file or directory related to bug N.
			"ext" can be anything.

   > 	bug-stuff-dir: .N

   Why required?

i'm presuming the tool that groks rfc822+subdir can be used for other
things than bugs; bug tracking is just one (simple) application.  i
agree that for bug tracking this kind of thing need not be specified.

thi

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


  reply	other threads:[~2002-03-25 22:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-24 20:23 More Bug Stuff Evan Prodromou
2002-03-24 23:03 ` Marius Vollmer
2002-03-25  8:21   ` Thien-Thi Nguyen
2002-03-25 15:48     ` Rob Browning
2002-03-25 21:19       ` Thien-Thi Nguyen
2002-03-25 21:35     ` Marius Vollmer
2002-03-25 22:00       ` Thien-Thi Nguyen [this message]
2002-03-25 22:03       ` Thien-Thi Nguyen
2002-03-25 22:25         ` Marius Vollmer
2002-03-27  0:31       ` Evan Prodromou
2002-03-27  2:58         ` Thien-Thi Nguyen
2002-03-27 19:09           ` Marius Vollmer
2002-03-27 20:39             ` Thien-Thi Nguyen
2002-04-07 11:17               ` Marius Vollmer
2002-04-07 19:05                 ` Thien-Thi Nguyen
2002-04-07 21:22                   ` Thien-Thi Nguyen
2002-04-07 21:38                   ` Marius Vollmer
2002-03-27 18:56         ` Marius Vollmer
2002-03-28 16:52   ` Evan Prodromou
2002-03-29  4:02     ` Thien-Thi Nguyen
2002-04-07 12:03     ` Marius Vollmer
2002-04-07 22:22       ` Thien-Thi Nguyen

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=E16pcVf-0001rM-00@colo.agora-net.com \
    --to=ttn@glug.org \
    --cc=evan@glug.org \
    --cc=guile-devel@gnu.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).