From: Till Kamppeter <till.kamppeter@gmail.com>
To: printing-architecture@lists.linux-foundation.org,
lsb-discuss@lists.linux-foundation.org,
webdevel@linux-foundation.org
Subject: [Printing-architecture] Where should we track bugs in the LSB DDK?
Date: Fri, 16 May 2008 11:29:13 +0200 [thread overview]
Message-ID: <482D53E9.4030201@gmail.com> (raw)
Hi,
I got already the first bug report for the LSB DDK (Driver Development
Kit) by e-mail.
As there are two suitable bug tracking systems
- LSB: http://bugs.linuxbase.org/
- OpenPrinting: http://bugs.linux-foundation.org/ (Prod.: OpenPrinting)
I am in doubt where to report these bugs. WDYT? I would say it is better
located in the LSB bug tracker.
This shows also that we should have only one bug tracker for the Linux
Foundation. So bugs can be more easily moved, for example an LSB-DDK bug
from OpenPrinting to LSB.
Till
next reply other threads:[~2008-05-16 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 9:29 Till Kamppeter [this message]
2008-06-02 10:52 ` [Printing-architecture] Where should we track bugs in the LSB DDK? Till Kamppeter
2008-06-02 11:30 ` TORATANI Yasumasa
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=482D53E9.4030201@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=lsb-discuss@lists.linux-foundation.org \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=webdevel@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.