lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 23 Feb 2012 23:52:13 +0100
From:	Florian Mickler <>
To:	"Rafael J. Wysocki" <>
Cc:	David Miller <>,,,
Subject: Re: Regression tracking

On Mon, 23 Jan 2012 01:52:25 +0100
"Rafael J. Wysocki" <> wrote:

> On Sunday, January 22, 2012, David Miller wrote:
> > From: Maciej Rutecki <>
> > 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]

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists