Dear Jonathan,
first of all thank You for the prompt reply, the merging, the proper
command to directly report on this bug and sorry for the
inconvenience. However the #612712 kicked in ("UnicodeEncodeError:
'ascii' codec can't encode character u'\u201c' in position 734:
ordinal not in range(128)") therefore I'm going to use the webmail
interface.
I feel that the most important is finding where the regression is
introduced so fast forward to linux-image-3.0.0-2-amd64_3.0.0-6_amd64
and the only thing I can tell is that it is still free from this
problem.
I keep You updated.
Yours truly,
Csaba GAÁL
2012/2/5 Jonathan Nieder <jrnieder@gmail.com>
>
> merge 658670 658727
> quit
>
> Csaba GAAL wrote:
>
> > [To: submit@bugs.debian.org]
>
> For the future, you can followup by sending email to
> 658670@bugs.debian.org (for example using your mailer's "reply to all"
> feature), or, if you don't have a working email setup, by using
> "reportbug -N 658670". Submitting a separate new bug with each
> message just makes for more work on this end...
>
> [...]
> > Just a preview of what's coming: still linux-image-2.6.39-2-amd64_2.6.39-3_amd64
> > is free from this speed regression problem, however for the record I am going to
> > file separate reports for:
> > 1) linux-image-2.6.35-rc5-amd64_2.6.35~rc5-1~experimental.1_amd64
> > 2) linux-image-2.6.36-rc5-amd64_2.6.36~rc5-1~experimental.1_amd64
> > 3) linux-image-2.6.37-2-amd64_2.6.37-2_amd64
> > 4) linux-image-2.6.38-2-amd64_2.6.38-5_amd64
> > 5) linux-image-2.6.39-2-amd64_2.6.39-3_amd64
>
> No thank you. So, which is the first version with the speed degredation?
>
> Thanks for the quick followup.
>
> Sincerely,
> Jonathan