Hi all,
We definitely aren't 100% in business yet with the tracking of regressions,
but since the Bugzilla is operational again, we can collect reports at least.
I'd like to use this opportunity to thank Maciej Rutecki and Florian Mickler
for their hard work on the regression tracking and to
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
From: Rafael J. Wysocki r...@sisk.pl
Date: Thu, 23 Feb 2012 23:51:25 +0100 (CET)
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should
This message contains a list of some post-3.1 regressions introduced before
3.2, for which there are no fixes in the mainline known to the tracking team.
If any of them have been fixed already, please let us know.
If you know of any other unresolved post-3.1 regressions, please let us know
either
This message has been generated automatically as a part of a report
of regressions introduced between 3.1 and 3.2.
The following bug entry is on the current list of known regressions
introduced between 3.1 and 3.2. Please verify if it still should
be listed and let the tracking team know (either
This message has been generated automatically as a part of a report
of regressions introduced between 3.1 and 3.2.
The following bug entry is on the current list of known regressions
introduced between 3.1 and 3.2. Please verify if it still should
be listed and let the tracking team know (either
This message has been generated automatically as a part of a report
of regressions introduced between 3.1 and 3.2.
The following bug entry is on the current list of known regressions
introduced between 3.1 and 3.2. Please verify if it still should
be listed and let the tracking team know (either
This message has been generated automatically as a part of a report
of regressions introduced between 3.1 and 3.2.
The following bug entry is on the current list of known regressions
introduced between 3.1 and 3.2. Please verify if it still should
be listed and let the tracking team know (either
This message has been generated automatically as a part of a report
of regressions introduced between 3.1 and 3.2.
The following bug entry is on the current list of known regressions
introduced between 3.1 and 3.2. Please verify if it still should
be listed and let the tracking team know (either
This message has been generated automatically as a part of a report
of regressions introduced between 3.1 and 3.2.
The following bug entry is on the current list of known regressions
introduced between 3.1 and 3.2. Please verify if it still should
be listed and let the tracking team know (either
This message has been generated automatically as a part of a report
of regressions introduced between 3.1 and 3.2.
The following bug entry is on the current list of known regressions
introduced between 3.1 and 3.2. Please verify if it still should
be listed and let the tracking team know (either
This message has been generated automatically as a part of a report
of regressions introduced between 3.1 and 3.2.
The following bug entry is on the current list of known regressions
introduced between 3.1 and 3.2. Please verify if it still should
be listed and let the tracking team know (either
From: Rafael J. Wysocki r...@sisk.pl
Date: Thu, 23 Feb 2012 23:51:20 +0100 (CET)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=42776
Subject : OF-related boot crash in 3.3.0-rc3-00188-g3ec1e88
Submitter : Meelis Roos mr...@linux.ee
Date : 2012-02-13
On Friday, February 24, 2012, David Miller wrote:
From: Rafael J. Wysocki r...@sisk.pl
Date: Thu, 23 Feb 2012 23:51:25 +0100 (CET)
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known
On Thu, Feb 23, 2012 at 11:55:57PM +0100, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and
27 matches
Mail list logo