On Thu, Feb 10, 2005 at 09:07:00AM +0100, Ingo Strüwing wrote: > Am Donnerstag, den 10.02.2005, 10:33 +0900 schrieb Horms: > > On Wed, Feb 09, 2005 at 04:50:49PM +0100, Ingo Strüwing wrote: > > > I have additional information: > > > > > > - The problem exists in 2.6.10 too. (BTW. should I report it there too?) > > > - The problem exists on ext3 filesystems too. > > > - The problem does not exist in 2.4.27. > > > > Thanks, all good information. You should probably just reasign the bug > > to kernel-source-2.6.10 as 2.6.9 is slowly on its way out of the debian > > tree. > > What does 'reasign' mean? Is there a way to move a report from one > packet to another? Or is it just reporting it again against 2.6.10?
Yes, you can move the bug. http://www.debian.org/Bugs/server-control Or someone else (like say, me) can do it for you. > > Also any feedback on 2.6.8 would be good, that is the target for sarge, > > 2.6.10 is just in sid for people to experiment and so we can > > see what has been fixed upstream when problems crop up in 2.6.8. > > In my original report I mentioned that I watched the behaviour in 2.6.8 Sorry, I missed that. > and 2.6.7 too. There may be a new version of 2.6.8 available though. > When I have your answer to the above question, I'll make a new 2.6.8 > kernel, test and report accordingly. Yes, there have been 3 updates to 2.6.8 since your report on December 22nd. The current version is 2.6.8-13. -- Horms
