Re: [PATCH v2 000/142] Use the $( ... ) construct for command substitution instead of using the back-quotes

3 messages, 3 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH v2 000/142] Use the $( ... ) construct for command substitution instead of using the back-quotes

From: Matthieu Moy <hidden>
Date: 2016-06-15 23:00:32

Junio C Hamano [off-list ref] 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/

Re: [PATCH v2 000/142] Use the $( ... ) construct for command substitution instead of using the back-quotes

From: Eric Sunshine <hidden>
Date: 2016-06-15 23:00:32

On Wed, Mar 26, 2014 at 3:02 AM, Matthieu Moy
[off-list ref] wrote:
Junio C Hamano [off-list ref] writes:
quoted
 - 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.

Re: [PATCH v2 000/142] Use the $( ... ) construct for command substitution instead of using the back-quotes

From: Elia Pinto <hidden>
Date: 2016-06-15 23:00:32

2014-03-26 8:44 GMT+01:00 Eric Sunshine [off-list ref]:
On Wed, Mar 26, 2014 at 3:02 AM, Matthieu Moy
[off-list ref] wrote:
quoted
Junio C Hamano [off-list ref] writes:
quoted
 - 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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help