> >I've tried that for lots of patches through the years. I'm
trying something
> >a bit different this time to see if I have any better luck.
It's an experiment
> >if you will.
>
> I'm not sure you're going to have much success
> since ultimately someone should be opening a
> bugzilla report. All you're doing is making more work for committers
>
> Interestingly, you didn't supply the key piece of
> information I requested. Reproducibility steps.
I understand from the above that you agree that it has been determined
that this is broken by inspection(and some cursory testing).
Surely it's not necessary to reproducability steps any more than
e.g. fresh regression testing cases for code that it is agreed is
broken by inspection?
I'll open a bugzilla report for this problem if there is consensus that
this should be fixed and that it can be agreed upon that it is broken.
In terms of testcase/reproducability, I'd go for a JUnit(or equivalent) test
for something like this. I don't know how to formulate such a test.
