On Tue, 26 Oct 2010, Julia Lawall wrote: > From: Julia Lawall <julia@xxxxxxx> > > Delete successive assignments to the same location. There are often results of mismerges or other assorted screw ups, often done by the maintainer itself (e.g. me in thinkpad-acpi's case) during development. The patch is correct, and I thank you for the head's up. But let me track down what caused it first, hmm? I also highly recommend that this should be done in all cases you find, instead of just blindly fixing the assignment. I suggest using git --blame to track down what added the duplicated assignments, and check if it looks sane... It is often a VERY BAD IDEA to remove such markers of potential brokennes without checking out if they're actually helpfully trying to warn you of worse badness :p But hey, maybe you've already done that. If you did, I apologise for preaching to the choir. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
