On Mon, 23 Jan 2012 01:52:25 +0100
"Rafael J. Wysocki" <[email protected]> wrote:
> On Sunday, January 22, 2012, David Miller wrote:
> > From: Maciej Rutecki <[email protected]>
> > Date: Sun, 22 Jan 2012 20:52:02 +0100
> >
> > > OK. But tracking regressions in two (or more) places is nonsense. And this
> > > puts into question all of my current work, such as how to analyze
> > > (automatically) the progress of the whole kernel and its quality per each -rc.
> > > Problem to discussion, but if everyone will do as you wish, it will all work
> > > went to waste.
> >
> > If someone else wants to maintain the state of bugs on some web
> > site and click buttons all day long, that is their perogative.
> >
> > But it's not something I'm going to do.
> >
> > You can't force people to use tools, and frankly that's the end of
> > this conversation as far as I'm concerned.
What I would like to ask from you and other developers in order to make
life easier for all users reporting bugs and people tracking
regressions is to post a solution for an issue to the mail thread it
was first reported in. That way we can just read through that mail
thread and see that it is resolved.
Also if you are aware, that someone (Maciej!) did open a bug for an
issue, please(!) stick that number in the commit changelog. Full Url
would be wonderful for automated processing, but "bug [nr]" is
sufficient for manual scanning of the commit log.
If you don't do that, I fear that I will annoy you from time to time
with: "is this issue fixed already?" or "hey, what about that 4 month
old regression? Is it already fixed?". (And knowing netdev, it is of
course already fixed in 99.9% of the cases. So I just need the pointer
to the solution...)
[If I have much time at hand, I will even scan the mail chatter of the
people involved during the time frame the bug was reported, but that is
a tedious task... still I do that sometimes in order to avoid annoying
people with this silly stuff]
Regards,
Flo
On Thu, Feb 23, 2012 at 11:52:13PM +0100, Florian Mickler wrote:
> If you don't do that, I fear that I will annoy you from time to time
> with: "is this issue fixed already?" or "hey, what about that 4 month
> old regression? Is it already fixed?".
If you intend to do this, please add me to your "do not mail" list.
For people working at distributions acting as middle-man, this isn't
helpful at all. And it's just not feasible for me to go dig out every
thread I posted to just to reply with "fixed".
Dave
On Thu, 23 Feb 2012 18:05:32 -0500
Dave Jones <[email protected]> wrote:
> On Thu, Feb 23, 2012 at 11:52:13PM +0100, Florian Mickler wrote:
>
> > If you don't do that, I fear that I will annoy you from time to time
> > with: "is this issue fixed already?" or "hey, what about that 4 month
> > old regression? Is it already fixed?".
>
> If you intend to do this, please add me to your "do not mail" list.
>
> For people working at distributions acting as middle-man, this isn't
> helpful at all. And it's just not feasible for me to go dig out every
> thread I posted to just to reply with "fixed".
>
> Dave
>
You are not on my go-to-guy list since you do not maintain a kernel
subsystem and I don't expect you to keep track of anything. If you post
a link to a rh-bugzilla, I will of course check if that one is still
open or how it is closed. I'm not stupid, I just need some
silver linen threads to find how a regression is solved.
I.e. I don't want a "fixed". I want a "commit xyz fixed this"
or a "I can't reproduce the bug anymore". Either is fine.