From: <benn.newman@snc.edu>
To: Fans of Plan 9 <9fans@cse.psu.edu>
Subject: [9fans] Issue tracking system
Date: Mon, 9 Jul 2007 09:03:21 -0500 [thread overview]
Message-ID: <20070709090321.SQB9J.50744.root@webfep13> (raw)
/n/sources/contrib/btdn/src/issue
I have hacked together an issue tracking system based on patch(1).
A new issue is created in the directory unconfirmed. It can then be commented
on or moved to other directories (I arbitrarily decided on--with a little help
from Bugzilla--on closed, confirmed, resolved, and wontfix.)
It doesn't do anything else.
I think that this is more open then e-mailing 9trouble@ and easier then using a
random page on the wiki.
--
Benjamin Newman
reply other threads:[~2007-07-09 14:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070709090321.SQB9J.50744.root@webfep13 \
--to=benn.newman@snc.edu \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).