From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] Public Bugzilla
Date: Fri, 4 Sep 2009 16:19:34 +0200 [thread overview]
Message-ID: <20090904141934.GC8060@barkeeper1-xen.linbit> (raw)
In-Reply-To: <20090904135205.GT12157@bla.fasel.org>
On Fri, Sep 04, 2009 at 03:52:05PM +0200, Wolfram Schlich wrote:
> Dear Linbit folks,
>
> as you are nowadays referencing bug numbers inside the DRBD
> changelogs, what about a publicly accessible Bugzilla?
Maybe.
Maybe not.
;)
If you ask me, I'd rather have (supposed to be) bugs reported on the
mailing list (drbd-user) or via the LINBIT support channels (Customers
only, obviously), than have a public bugzilla.
I fear that a public bugzilla would just depleat our limited time pool
yet again, by endless reports of "does not feed my cat, either".
> Is there any other incarnation of a publicly available list
> of bugs and the corresponding descriptions?
Nope.
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
next prev parent reply other threads:[~2009-09-04 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 13:52 [Drbd-dev] Public Bugzilla Wolfram Schlich
2009-09-04 14:19 ` Lars Ellenberg [this message]
2009-09-04 14:25 ` Wolfram Schlich
2009-09-04 15:14 ` Lars Ellenberg
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=20090904141934.GC8060@barkeeper1-xen.linbit \
--to=lars.ellenberg@linbit.com \
--cc=drbd-dev@lists.linbit.com \
/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