| 2006-07-10 14:59:45 |
Onkar Shinde |
bug |
|
|
added bug |
| 2006-07-10 19:01:55 |
ajack2001my |
dapper-backports: status |
Unconfirmed |
Confirmed |
|
| 2006-07-10 19:01:55 |
ajack2001my |
dapper-backports: statusexplanation |
|
|
|
| 2006-07-13 13:11:02 |
John Dong |
dapper-backports: status |
Confirmed |
Unconfirmed |
|
| 2006-07-13 13:11:02 |
John Dong |
dapper-backports: statusexplanation |
|
(re-marking as unconfirmed)
How does Alsa backporting work? I was always under the impression that doing so requires appropriate changes/alsa patches in the kernel, correct? |
|
| 2006-07-13 13:44:07 |
John Dong |
dapper-backports: status |
Unconfirmed |
Rejected |
|
| 2006-07-13 13:44:07 |
John Dong |
dapper-backports: statusexplanation |
(re-marking as unconfirmed)
How does Alsa backporting work? I was always under the impression that doing so requires appropriate changes/alsa patches in the kernel, correct? |
Then, unfortunately, I will not be able to do it.
The kernel is still open for "bugfixes", so I'll subscribe this bug over to the kernel team and see what they think.
I'm sorry about this. |
|
| 2006-07-13 13:44:53 |
John Dong |
bug |
|
|
assigned to linux-source-2.6.15 (Ubuntu) |
| 2006-07-13 16:29:01 |
Ben Collins |
linux-source-2.6.15: status |
Unconfirmed |
Rejected |
|
| 2006-07-13 16:29:01 |
Ben Collins |
linux-source-2.6.15: statusexplanation |
|
Rejecting on the basis that most of the patches in current alsa are actually in dapper kernel.
If there's some specific problem, please search the bug reports to see if it is already reported, or open a new bug report. A complete backport of the entire alsa tree will not happen for dapper, and certainly will not be done just to satisfy one problem by one user. |
|
