Re: New (now current development process)
From: Krzysztof Halasa (khc_at_pm.waw.pl)
Date: 11/07/05
- Previous message: Christopher Friesen: "Re: scheduler parameter inheritance on clone() -- correction"
- In reply to: Christopher Friesen: "Re: New (now current development process)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: "Christopher Friesen" <cfriesen@nortel.com> Date: Mon, 07 Nov 2005 19:25:35 +0100
"Christopher Friesen" <cfriesen@nortel.com> writes:
> How do you ever know that new change introduced no new bugs?
Changing comments doesn't change generated code or your tools are
screwed. Trivial changes - you can be reasonably sure, too. Note
it's different from not having bugs at all.
> Maybe
> there was a latent race condition that is activated by timing
> differences caused by the new code.
Then the bug already existed, you aren't adding any.
> The safe bet is to simply rename the final -rc with no further changes.
Safe? You can't be really safe here. Bad luck and version string
change (compile time or -rc* removal) will trigger disaster.
-- Krzysztof Halasa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Christopher Friesen: "Re: scheduler parameter inheritance on clone() -- correction"
- In reply to: Christopher Friesen: "Re: New (now current development process)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|