Mark Linimon <[EMAIL PROTECTED]> writes: > (This is just a view from the sidelines; I generally do ports hacking > and not kernel hacking, and thus my views might not carry much > weight, but here goes anyways). > > One of the more interesting features of the FreeBSD development > model seems to me to be the ability for people to request controversial > CVS commits to be backed out pending further technical discussion. > IMHO this seems like a wise (albeit nonintuitive) plan to avoid > meta-discussions about what should and should not have been > committed by whom and reviewed by whom (and so on and so forth). > > But recently (especially since the 5.0 release) the backout request > mechanism seems to have fallen on hard times. Without too much > difficulty, I was able to find 5 separate backout requests in this > year's archive of cvs-all alone which were not quickly honored. > (I'm not counting an ignored request for which the underlying > change was apparently security-related). I'm not sure, but there > may have been others, possibly on freebsd-current.
The archives might not be telling the whole story. A lot of times these things get handled behind closed doors, whether private e-mail or developer-only lists. Thankfully though, most conflicts *do* get resolved. :) Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
