You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by yl...@apache.org on 2016/03/30 13:32:40 UTC

svn propchange: r1737103 - svn:log

Author: ylavic
Revision: 1737103
Modified property: svn:log

Modified: svn:log at Wed Mar 30 11:32:40 2016
------------------------------------------------------------------------------
--- svn:log (original)
+++ svn:log Wed Mar 30 11:32:40 2016
@@ -1 +1 @@
-core: 'xauth list|grep yl4p |awk '{print }' == 0' => 'x != 0' to avoid a compiler warning (suggesting parens).
+core: '!x == 0' => 'x != 0' to avoid a compiler warning (suggesting parens).


Re: svn propchange: r1737103 - svn:log

Posted by Stefan Eissing <st...@greenbytes.de>.
Let me know when your shell interprets my log messages...

> Am 30.03.2016 um 13:35 schrieb Yann Ylavic <yl...@gmail.com>:
> 
> On Wed, Mar 30, 2016 at 1:32 PM,  <yl...@apache.org> wrote:
>> Author: ylavic
>> Revision: 1737103
>> Modified property: svn:log
>> 
>> Modified: svn:log at Wed Mar 30 11:32:40 2016
>> ------------------------------------------------------------------------------
>> --- svn:log (original)
>> +++ svn:log Wed Mar 30 11:32:40 2016
>> @@ -1 +1 @@
>> -core: 'xauth list|grep yl4p |awk '{print }' == 0' => 'x != 0' to avoid a compiler warning (suggesting parens).
>> +core: '!x == 0' => 'x != 0' to avoid a compiler warning (suggesting parens).
> 
> Oups, somehow my shell interpreted the exclamation mark in the command line :)


Re: svn propchange: r1737103 - svn:log

Posted by Yann Ylavic <yl...@gmail.com>.
On Wed, Mar 30, 2016 at 1:32 PM,  <yl...@apache.org> wrote:
> Author: ylavic
> Revision: 1737103
> Modified property: svn:log
>
> Modified: svn:log at Wed Mar 30 11:32:40 2016
> ------------------------------------------------------------------------------
> --- svn:log (original)
> +++ svn:log Wed Mar 30 11:32:40 2016
> @@ -1 +1 @@
> -core: 'xauth list|grep yl4p |awk '{print }' == 0' => 'x != 0' to avoid a compiler warning (suggesting parens).
> +core: '!x == 0' => 'x != 0' to avoid a compiler warning (suggesting parens).

Oups, somehow my shell interpreted the exclamation mark in the command line :)