Re: Bug reporting script? (was: removal of redundant line in documentation)

2001-01-11 Thread Pavel Machek
Hi! > > This is horrible bugreport. Kill "keywords". Putting "modules" into > > keywords i not going to help anyone. Having "4. Kernel version" and > > minuses before actuall version is not helpfull, either. > > "modules" as keyword, keywords in general: This is a suggestion from > REPORTING-BUG

Re: Bug reporting script? (was: removal of redundant line in documentation)

2001-01-09 Thread Pavel Machek
Hi! > > If ver_linux can take off one of those steps, why not include a script > > which takes care of ALL the leg work? All of the files it asks the > > reporter to include are o+r... > > If have started a script that produces the following output. ( some fields > need to be filled, but the str

Re: Bug reporting script? (was: removal of redundant line in documentation)

2001-01-06 Thread db
[...] > About bug reports, isn't a good thing introduce the sgi's lkcd (linux kernel crash dump) into the main stream of 2.5? The main problem of lkcd in 2.2 was the lack of kiobufs. > > I think it as a good thing, for distributions, the distribution guys have the vmlinuz image of the distro, so

Re: Bug reporting script? (was: removal of redundant line in documentation)

2001-01-06 Thread Augusto César Radtke
Jeremy M. Dolan wrote: > If ver_linux can take off one of those steps, why not include a script > which takes care of ALL the leg work? All of the files it asks the > reporter to include are o+r... > > I can whip up a bug_report script to walk the user though all of the > steps in REPORTING-BUGS

Bug reporting script? (was: removal of redundant line in documentation)

2001-01-05 Thread Jeremy M. Dolan
On Sat, 06 Jan 2001 06:51:58 +, Matthias Juchem wrote: > Step [7.3] is redundant because it is > already handled by the ver_linux script If ver_linux can take off one of those steps, why not include a script which takes care of ALL the leg work? All of the files it asks the reporter to includ