Mailinglist Archive: opensuse-factory (818 mails)
| < Previous | Next > |
Re: [opensuse-factory] Bug 431880 closed as duplicate of 431542 - which is marked as private
- From: "Andrew Joakimsen" <joakimsen@xxxxxxxxx>
- Date: Sun, 26 Oct 2008 23:42:01 -0400
- Message-id: <23fd749a0810262042g6c883e08y600dac87b2323bb2@xxxxxxxxxxxxxx>
On Wed, Oct 15, 2008 at 12:27 PM, Andrew Joakimsen <joakimsen@xxxxxxxxx> wrote:
Hello Dirk:
I still do not have access to bug 433553, which is a "duplicate" of a
bug I reported against SLED Beta 2. The bug I reported, No. 434541 is
not resolved in Beta 3, even though it says the fix was "committed"
23rd October.
Anyways, without access to the original bug I have no idea if this is
even related to the issue I am seeing.
Furthermore I wish to express my concerns, why is a bug relating to
keys on a keyboard for a feature that works on some hardware in 10.x
need to be marked "private?" This is only making more work for your
developers and also for us who then need to go back and verify because
the bug is a "black box" there is no way to know if the issue truly is
a duplicate.
Warmest regards,
Andrew
On Fri, Oct 10, 2008 at 6:16 AM, Dirk Müller <dmueller@xxxxxxx> wrote:
In the meantime, if there is any bugreport where you think you should have
access but don't, feel free to mail me privately and ask about it.
433553; xxxxxx@xxxxxxxxx
Reported originally as 434541 by me.
Hello Dirk:
I still do not have access to bug 433553, which is a "duplicate" of a
bug I reported against SLED Beta 2. The bug I reported, No. 434541 is
not resolved in Beta 3, even though it says the fix was "committed"
23rd October.
Anyways, without access to the original bug I have no idea if this is
even related to the issue I am seeing.
Furthermore I wish to express my concerns, why is a bug relating to
keys on a keyboard for a feature that works on some hardware in 10.x
need to be marked "private?" This is only making more work for your
developers and also for us who then need to go back and verify because
the bug is a "black box" there is no way to know if the issue truly is
a duplicate.
Warmest regards,
Andrew
| < Previous | Next > |