2.6.25-rc8: FTP transfer errors
Quoted 4 lines
Sure. It's not about bisection specifically, but about the time a reporter is able to invest in addition to what went into the report already. But bisection is is a good example, because it's the most time-consuming of all the tasks routinely asked from bug reporters.
i think the problem with git-bisect is, that it just apears complicated and magic for an end-user. this isn`t something a kernel-developer can explain to him in a sentence (i.e. how to use etc)
at short: i think this scares non-developers (=end users) away. git is for developers, not for end-users.
its up to the user to get into that and thats something a user probably doesnt dare and also doesnt want.
he has a bug and want`s this resolved.
its very valuable if he reported the problem on lkml at all (many users just dont care, many just don't dare posting mails reaching that big audience), but it would be really BAD if nothing more happens just because the user isn`t willing to spend an evening or more to dig into a bug being introduced by some commit months ago.
its that sort of "it worked for me for years and now it doesnt work anymore. please make it work as before".
you know that ibm virtualization ad (the heist) from years ago? it`s also that "how do i know? youŽ re the cops!" - thing.
what about making it more trivial for non-developers by providing a type of "dummy's interface to git bisect" ?
some "please use the script which helps you find the change that may introduced the bug by binary search at /usr/src/linux/scripts...."
maybe it could look like this:
1. you don`t have git on this box. please install git (see http://.....)
2. what was the last known kernel version which worked for you ?
3. what was the first kernel version which showed the problem you reported ?
<now git bisect machinery runs behind the scene and the user doesn`t need to learn git/bisect at all>
4. now please try this kernel build
<test>
5. did it work for you (y/n)
.....
many software companies have some type of support-script for their software, to make it easy to collect all the important data - so maybe it would give a sense to make it easier for the end-user to use git-bisect ?
regards
roland
ps:
good article on this, btw:
http://www.linuxworld.com/news/2007/112007-kernel.html?page=3
Quoted 6 lines · Evgeniy Polyakov
Quoted 3 lines · Tilman Schmidt
So I was right after all? Bug reports from people who (for whatever reason, including having to earn their living) cannot do a bisect are not welcome?
You got it wrong.
Did I really? Let's see ...
Quoted 6 lines
If bug is subtle and developers can not reproduce it, there are only two ways out of the problem: to help developers or not to help.
In the latter case bug report is useless (except that to show that it exists, since practically no one can fix it until some new details added).
Looks like you're saying I was right after all. Useless bug reports shouldn't be submitted.
So please answer this simple question: If I know beforehand that I won't have the time to do a bisect (or other similarly time-consuming task the maintainers might ask from me), should I report the bug, or should I keep my knowledge to myself?
This question is not theoretical. It's a situation I find myself in quite regularly, because I allow myself the luxury of building most rc kernels and even the odd mm kernel just for fun even though I have a daytime job and a family to feed. It would be quite easy to look the other way if I encounter a problem in one of those, hoping someone else with more time on his or her hands will also come across it and report it. So far my conscience told me not to do that. But if reporting it without being able to follow up on it is considered useless then my conscience was apparently wrong. Just say the word, and I'll stop what I'm doing. I'll have no problem finding other things to do with my time.
Quoted 1 line
Bisection was just an example of the help, reporter can provide.
Sure. It's not about bisection specifically, but about the time a reporter is able to invest in addition to what went into the report already. But bisection is is a good example, because it's the most time-consuming of all the tasks routinely asked from bug reporters.
Quoted 2 lines
If you can not proceed with what was suggested, then do not piss anyone off because you were told to do something to help.
If a polite "sorry, I don't have the time" already counts as pissing off, the only choice left is to avoid the situation in which I'd have to say that. IOW, don't report bugs if I don't have the time to follow through. Again: if that is what you want, I have no problem with it.
Quoted 2 lines
If you go to the doctor because of aching throat and he asks you to open a mouth, you will not blame him for asking you to do that.
That analogy is wrong on so many accounts. It is not my throat that's aching. A doctor would not insult me for not wanting to open my mouth but rather ask if there was perhaps a valid reason for that. Not to mention that opening my mouth takes substantially less time than a Linux kernel bisection ...
A better analogy would be if I see an object lying on the highway, and I stop at the next service area to call the police and alert them about the possible danger. If they'd ask me to drive back to the place where I saw it in order to describe precisely where it lay and what it looked like, I think I might indeed become a bit upset.
HTH
T.
PS: I'll shut my big mouth now. The topic has been beaten to death.
__________________________________________________
GRATIS: Movie-FLAT. Jetzt freischalten!
http://freemail.web.de/club/maxdome.htm/?mc=025557
Quoted 8 lines · On Sat, Apr 12, 2008 at 10:41:44AM +0200, [email protected] wrote:
Quoted 4 lines
Sure. It's not about bisection specifically, but about the time a reporter is able to invest in addition to what went into the report already. But bisection is is a good example, because it's the most time-consuming of all the tasks routinely asked from bug reporters.
i think the problem with git-bisect is, that it just apears complicated and magic for an end-user. this isn`t something a kernel-developer can explain to him in a sentence (i.e. how to use etc)
...
When I ask a user to bisect, the standard boilerplate I give to the user is:
<-- snip -->
# install git
# clone Linus' tree: git clone \ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
# start bisecting: cd linux-2.6 git bisect start git bisect bad v2.6.21 git bisect good v2.6.20 cp /path/to/.config .
# start a round make oldconfig make # install kernel, check whether it's good or bad, then: git bisect [bad|good] # start next round
After at about 10-15 reboots you'll have found the guilty commit ("... is first bad commit").
More information on git bisecting:
man git-bisect
<-- snip -->
In my experience users are able to bisect with this boilerplate (unless there are problems like e.g. other regressions hit during bisecting).
Quoted 3 lines
regards
roland
...
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed