From: "Daniel Weismüller" <whytea@ipfire.org>
To: documentation@lists.ipfire.org
Subject: [Documentation] new list in bugzilla
Date: Tue, 06 Mar 2012 08:05:01 +0100 [thread overview]
Message-ID: <4F55B71D.7090807@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
Hello!
In bugziila we now have our own "buglist".
https://bugzilla.ipfire.org/describecomponents.cgi
The idea is that every one of us may write down what should be done and
we are able to assign it to someone.
Further we have quick overview of the work that must be done.
What you think about it?
- Daniel
--
__________________________________________
You need a firewall?
Easy to use? Powerful? Modular? For free?
www.ipfire.org
An Open Source Firewall Solution
next reply other threads:[~2012-03-06 7:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 7:05 Daniel Weismüller [this message]
2012-03-06 8:48 ` Michael Tremer
2012-03-06 14:26 ` Daniel Weismüller
2012-03-06 14:43 ` Michael Tremer
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=4F55B71D.7090807@ipfire.org \
--to=whytea@ipfire.org \
--cc=documentation@lists.ipfire.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