Actually my dream in life is to do reports based on bug lifespan (i.e. time between a bug was filed till it was closed) -- I'm interested in how this number varies with bug severity, who filed it, yada yada. The problem is there is no good way to measure this time.
I'm a little lost on what the different files do -- do mboxes exist for all bugs? I've been relying on the log/summary files assuming that everything I need to find should be there -- do you have a better idea? Abhishek On Wed, Apr 20, 2011 at 1:15 PM, Olivier Berger <[email protected]> wrote: > Hi. > > Le mercredi 20 avril 2011 à 11:27 -0400, Abhishek a écrit : >> Hola Folks, >> >> My dream in life at this point in time is to be able to recreate a bug >> modification history from the log / report / summary files. >> Something like what bugzilla does -- >> https://bugzilla.kernel.org/show_activity.cgi?id=12 >> > > What exactly are you trying to achieve... I guess if it's your dream in > life, then you probably have a greater goal than just reconstructing a > bug's history. > >> >From what I understand the way debbugs logs things has changed. These >> are my questions: >> >> a) what seems like the best way to do this? (i.e. what string patterns >> I should be looking for) > > Unless that's already obvious, I guess the reference information about > bugs should be found in the mbox of the bug, as commands to debbugs are > issued by email. > > Hope this helps. > > Best regards, > > P.S.: if it's related to SD, yes, that's quite interesting ! ;-) > -- > Olivier BERGER <[email protected]> > http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 > Ingénieur Recherche - Dept INF > Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France) > > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/BANLkTimqHADK8oGHSpPC4ú[email protected]
