Re: [PATCH v2 000/142] Use the $( ... ) construct for command substitution instead of using the back-quotes
Junio C Hamano gits...@pobox.com writes: - Nobody has time or energy to go through 140+ patches in one go, with enough concentration necessary to do so without making mistakes (this applies to yourself, too---producing mechanical replacement is a no-cost thing, finding mistakes in mechanical replacement takes real effort). It's a bit less bad than it seems: 142 files changed, 609 insertions(+), 609 deletions(-) The first pass I did was a very quick one, but I already went through the patches I received (apparently not the whole series) and it wasn't that long. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 000/142] Use the $( ... ) construct for command substitution instead of using the back-quotes
On Wed, Mar 26, 2014 at 3:02 AM, Matthieu Moy matthieu@grenoble-inp.fr wrote: Junio C Hamano gits...@pobox.com writes: - Nobody has time or energy to go through 140+ patches in one go, with enough concentration necessary to do so without making mistakes (this applies to yourself, too---producing mechanical replacement is a no-cost thing, finding mistakes in mechanical replacement takes real effort). It's a bit less bad than it seems: 142 files changed, 609 insertions(+), 609 deletions(-) The first pass I did was a very quick one, but I already went through the patches I received (apparently not the whole series) and it wasn't that long. I also gave v2 a read-through. Nothing jumped out as a red-flag. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 000/142] Use the $( ... ) construct for command substitution instead of using the back-quotes
2014-03-26 8:44 GMT+01:00 Eric Sunshine sunsh...@sunshineco.com: On Wed, Mar 26, 2014 at 3:02 AM, Matthieu Moy matthieu@grenoble-inp.fr wrote: Junio C Hamano gits...@pobox.com writes: - Nobody has time or energy to go through 140+ patches in one go, with enough concentration necessary to do so without making mistakes (this applies to yourself, too---producing mechanical replacement is a no-cost thing, finding mistakes in mechanical replacement takes real effort). It's a bit less bad than it seems: 142 files changed, 609 insertions(+), 609 deletions(-) The first pass I did was a very quick one, but I already went through the patches I received (apparently not the whole series) and it wasn't that long. I also gave v2 a read-through. Nothing jumped out as a red-flag. Thank you all. I will change the comment as the maintainer wishes (75ee3d7078fbcc3b87a3ae5e0cf42f46256c5da4 for example) and send the other patches slowly (10 at a time every week, boring but that's okay). Best Regards -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 000/142] Use the $( ... ) construct for command substitution instead of using the back-quotes
Elia Pinto gitter.spi...@gmail.com writes: This is a second reroll after the Matthieu Moy review. Changes from v1: - Dropped the silly patches to t6111-rev-list-treesame.sh, t0204-gettext-reencode-sanity.sh. - Simple reformatting of the commit message. - added the toy script used for doing the patch. In other words, Mattheiu pointed out two examples of breakages and they were the only mistakes after you re-reviewed the mechanical changes, and there is no more? - Cleaning up is a good thing, but - Mechanical and mindless conversion is always error-prone, and - Eyeballing each and every change is required, but - Nobody has time or energy to go through 140+ patches in one go, with enough concentration necessary to do so without making mistakes (this applies to yourself, too---producing mechanical replacement is a no-cost thing, finding mistakes in mechanical replacement takes real effort). That is why we strongly discourage people from such a whole-tree clean-up just for the sake of clean-up and nothing else, and instead encourage them to clean-up as a preparatory step for real work on the files involved. Sure, it would not give us as wide a coverage as a mechanical whole-tree replacement in one-go, but that is the only practical way to avoid mistakes. If it were four patches per every Monday kind of trickle, we might be able to spend some review bandwidth while reviewing other patches, though. So I am not very enthused about reviewing and applying these patches in their current form. Thanks. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
