On Monday 22 March 2010, Hugh Dickins wrote:
On Sun, 21 Mar 2010, Rafael J. Wysocki wrote:
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. Please verify if it still should
be listed and let the tracking team know (either way).
On Tue, Mar 23, 2010 at 5:28 AM, Rafael J. Wysocki r...@sisk.pl wrote:
On Monday 22 March 2010, Hugh Dickins wrote:
On Sun, 21 Mar 2010, Rafael J. Wysocki wrote:
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. Please verify if it
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. Please verify if it still should
be listed and let the tracking team
On Sun, 21 Mar 2010, Rafael J. Wysocki wrote:
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. Please verify if it still should
be listed and let the tracking team know (either way).
Bug-Entry :
Hugh Dickins hugh.dick...@tiscali.co.uk writes:
On Mon, 22 Feb 2010, Américo Wang wrote:
On Mon, Feb 22, 2010 at 5:30 AM, Rafael J. Wysocki r...@sisk.pl wrote:
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is
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 2.6.32. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
On Mon, Feb 22, 2010 at 5:30 AM, Rafael J. Wysocki r...@sisk.pl 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 2.6.32. Please verify if it still should be
On Sun, 7 Feb 2010, 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 2.6.32. Please verify if it still should be listed and let the tracking
On Monday 08 February 2010, Hugh Dickins wrote:
On Sun, 7 Feb 2010, 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 2.6.32. Please
On Sun, 7 Feb 2010, Hugh Dickins 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 2.6.32. Please verify if it still should be listed and let the
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.32. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
11 matches
Mail list logo