{"thread":{"id":"16114","subject":"Re: [PATCH] Avoid using non-portable `echo -n` in tests.","startedAt":"2008-10-31T19:50:31Z","lastAt":"2008-10-31T20:30:02Z","messageCount":4,"participants":["Francis Galiegue","Junio C Hamano","Ian Hilt"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"94444","messageId":"200810312050.31167.fg@one2team.net","threadId":"16114","inReplyTo":null,"subject":"Re: [PATCH] Avoid using non-portable `echo -n` in tests.","fromName":"Francis Galiegue","fromEmail":"fg@one2team.net","sentAt":"2008-10-31T19:50:31Z","receivedAt":"2008-10-31T19:50:31Z","isPatch":true,"sender":{"key":"fg@one2team.net","avatar":null},"body":"Le Friday 31 October 2008 19:39:33 Jeff King, vous avez écrit :\n[...]\n>\n> Agreed, and actually I found such a bashism (test ==) last week (though\n> of course it also broke on FreeBSD).\n>\n\nAs for bash-isms, a hunt for $(...) also looks necessary...\n\n$ grep -rl '\\$([^)]\\+)' $(find -type f)|wc -l\n272\n\nUnless I'm mistaken (and I probably am), the $(...) construct is \nbash-specific, isn't it?\n\n-- \nfge\n"},{"id":"94449","messageId":"7vbpx08r1d.fsf@gitster.siamese.dyndns.org","threadId":"16114","inReplyTo":"200810312050.31167.fg@one2team.net","subject":"Re: [PATCH] Avoid using non-portable `echo -n` in tests.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-10-31T20:10:06Z","receivedAt":"2008-10-31T20:10:06Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Francis Galiegue <fg@one2team.net> writes:\n\n> Unless I'm mistaken (and I probably am), the $(...) construct is \n> bash-specific, isn't it?\n\nYou are.\n"},{"id":"94453","messageId":"20081031201127.GA21345@maintenance05.msc.mcgregor-surmount.com","threadId":"16114","inReplyTo":"200810312050.31167.fg@one2team.net","subject":"Re: [PATCH] Avoid using non-portable `echo -n` in tests.","fromName":"Ian Hilt","fromEmail":"ihilt@mcgregor-surmount.com","sentAt":"2008-10-31T20:11:27Z","receivedAt":"2008-10-31T20:11:27Z","isPatch":true,"sender":{"key":"ihilt@mcgregor-surmount.com","avatar":null},"body":"On Fri, Oct 31, 2008 at 08:50:31PM +0100, Francis Galiegue wrote:\n> Le Friday 31 October 2008 19:39:33 Jeff King, vous avez écrit :\n> [...]\n> >\n> > Agreed, and actually I found such a bashism (test ==) last week (though\n> > of course it also broke on FreeBSD).\n> >\n> \n> As for bash-isms, a hunt for $(...) also looks necessary...\n> \n> $ grep -rl '\\$([^)]\\+)' $(find -type f)|wc -l\n> 272\n> \n> Unless I'm mistaken (and I probably am), the $(...) construct is \n> bash-specific, isn't it?\n\nNope.  Read section 2.6.3 Command Substitution here,\n\n<http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html>\n"},{"id":"94455","messageId":"200810312130.03037.fg@one2team.net","threadId":"16114","inReplyTo":"20081031201127.GA21345@maintenance05.msc.mcgregor-surmount.com","subject":"Re: [PATCH] Avoid using non-portable `echo -n` in tests.","fromName":"Francis Galiegue","fromEmail":"fg@one2team.net","sentAt":"2008-10-31T20:30:02Z","receivedAt":"2008-10-31T20:30:02Z","isPatch":true,"sender":{"key":"fg@one2team.net","avatar":null},"body":"Le Friday 31 October 2008 21:11:27 Ian Hilt, vous avez écrit :\n[...]\n> >\n> > Unless I'm mistaken (and I probably am), the $(...) construct is\n> > bash-specific, isn't it?\n>\n> Nope.  Read section 2.6.3 Command Substitution here,\n>\n> <http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html>\n\nMy bad, then. I'm too \"old-school\", I guess ;)\n\n-- \nfge\n"}]}