reopen 506419
found 506419 linux-2.6/2.6.26-10
found 506419 linux-2.6/2.6.26-11
found 506419 linux-2.6/2.6.27
tags 506419 + upstream
owner 506419 !
quit
Ben Hutchings wrote:
I'm closing this because I think a year is more than enough time to test
a new version.
I'll take ownership then. I
also sprach Jonathan Nieder jrnie...@gmail.com [2011.03.24.0728 +0100]:
I'm closing this because I think a year is more than enough time to test
a new version.
I'll take ownership then. I used to have a forcedeth and while I
don't anymore, I'm interested in the driver being reliable.
martin f krafft wrote:
I still have the hardware, but it's on a production machine. It is
onboard and I added a separate NIC, so it's unused, but I cannot
really run kernel-level experiments.
However, the machine has KVM, and as soon as KVM supports PCI
passthrough, that might be useful.
On Thu, 2011-03-24 at 01:28 -0500, Jonathan Nieder wrote:
reopen 506419
found 506419 linux-2.6/2.6.26-10
found 506419 linux-2.6/2.6.26-11
found 506419 linux-2.6/2.6.27
tags 506419 + upstream
owner 506419 !
quit
Ben Hutchings wrote:
I'm closing this because I think a year is more than
Ben Hutchings wrote:
If you can't test it, what good does it to reopen the bug?
It is a real bug and I have no reason to believe it was fixed.
Meanwhile the submitter has said that as soon as circumstances allow,
he'll test it. Is the bug doing harm by sitting open? Perhaps
someone should
On Thu, Mar 24, 2011 at 04:18:41PM -0500, Jonathan Nieder wrote:
Ben Hutchings wrote:
If you can't test it, what good does it to reopen the bug?
It is a real bug and I have no reason to believe it was fixed.
It *was* a real bug and you have no reason to believe it is not fixed.
Ben Hutchings wrote:
It *was* a real bug and you have no reason to believe it is not fixed.
Sure, it is possible that 6c2da9c or eb10a781 fixes this. But I
really do suspect that it's not fixed. I'd take at least 1:1 odds.
New submitters are expected to look through existing bug reports.
7 matches
Mail list logo
