Bug#854416: Keep data for 24H for latest bugs in bugscan; fix time too

2017-02-06 Thread Francesco Poli
On Mon, 6 Feb 2017 15:42:08 -0600 Don Armstrong wrote: > On Mon, 06 Feb 2017, Francesco Poli wrote: > > On Mon, 6 Feb 2017 14:57:18 -0600 Don Armstrong wrote: > > > > [...] > > > On Mon, 06 Feb 2017, Francesco Poli wrote: > > > > I mean: too many data gets similar to the absence of data. > > > >

Bug#854416: Keep data for 24H for latest bugs in bugscan; fix time too

2017-02-06 Thread Don Armstrong
On Mon, 06 Feb 2017, Francesco Poli wrote: > On Mon, 6 Feb 2017 14:57:18 -0600 Don Armstrong wrote: > > [...] > > On Mon, 06 Feb 2017, Francesco Poli wrote: > > > I mean: too many data gets similar to the absence of data. > > > It often says "NO release-critical bugs were closed and NONE were > >

Bug#854416: Keep data for 24H for latest bugs in bugscan; fix time too

2017-02-06 Thread Francesco Poli
On Mon, 6 Feb 2017 14:57:18 -0600 Don Armstrong wrote: [...] > On Mon, 06 Feb 2017, Francesco Poli wrote: > > I mean: too many data gets similar to the absence of data. > > It often says "NO release-critical bugs were closed and NONE were > > opened." and many previous changes have already vanishe

Bug#854416: Keep data for 24H for latest bugs in bugscan; fix time too

2017-02-06 Thread Don Armstrong
Package: bugs.debian.org Severity: minor Control: submitter -1 Francesco Poli On Mon, 06 Feb 2017, Francesco Poli wrote: > I mean: too many data gets similar to the absence of data. > It often says "NO release-critical bugs were closed and NONE were > opened." and many previous changes have alrea