gt;>>>> soon
>>>>>>> as someone uses it, it will blow away manual changes. And if you had
>>>>>>> auto-generated the patch file, it probably wouldn't have had
>>>>>>> formatting
>>>>>>&
gt;>>> On 2/12/18, 8:26 AM, "Yishay Weiss" <yishayj...@hotmail.com
>>>> <mailto:yishayj...@hotmail.com <mailto:yishayj...@hotmail.com>>>
>>>>wrote:
>>>>
>>>>> Add, see my later mail.
>>>>>
ishayj...@hotmail.com>>> wrote:
>>>
>>>> Add, see my later mail.
>>>>
>>>> From: Gabe Harbs<mailto:harbs.li...@gmail.com
>>>> <mailto:harbs.li...@gmail.com>>
>>>> Sent: Monday, February 12, 2018 6:23 P
yj...@hotmail.com>> wrote:
>>
>>> Add, see my later mail.
>>>
>>> From: Gabe Harbs<mailto:harbs.li...@gmail.com>
>>> Sent: Monday, February 12, 2018 6:23 PM
>>> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
>&g
>> Sent: Monday, February 12, 2018 6:23 PM
>> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
>> Subject: Re: Build failed in Jenkins: royale-typedefs #139
>>
>> What was it? Did you add a space, or remove a space?
>>> On Feb 12, 2018, at 6:11 PM, Yi
Add, see my later mail.
From: Gabe Harbs<mailto:harbs.li...@gmail.com>
Sent: Monday, February 12, 2018 6:23 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: Build failed in Jenkins: royale-typedefs #139
What was it? Did you add a space, or remove a space?
>
day, February 12, 2018 5:18 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: Build failed in Jenkins: royale-typedefs #139
>
> Does anyone understand the patch file syntax enough to guess what’s wrong?
>
>> On Feb 12, 2018, at 5:15 PM, Yishay Weis
@gmail.com>
> Sent: Monday, February 12, 2018 5:18 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: Build failed in Jenkins: royale-typedefs #139
>
> Does anyone understand the patch file syntax enough to guess what’s wrong?
>
> > On Feb 12, 201
I fixed it for my machine. Hopefully Jenkins will be happy too.
From: Gabe Harbs<mailto:harbs.li...@gmail.com>
Sent: Monday, February 12, 2018 5:18 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: Build failed in Jenkins: royale-typedefs #139
Does anyon
ycki<mailto:piotrzarzyck...@gmail.com>
> Sent: Monday, February 12, 2018 3:13 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: Build failed in Jenkins: royale-typedefs #139
>
> Locally I have same result. I tried couple of things but nothing help. I
I have the same result with ant on my machine. It’s probably a windows/mac
thing.
From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
Sent: Monday, February 12, 2018 3:13 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: Build failed in Jenkins: royale-t
Locally I have same result. I tried couple of things but nothing help. I
see that it is being applied by following command:
[DEBUG] Executing command line: [C:\Program Files\Git\cmd\git.exe, apply,
--ignore-whitespace, --whitespace=nowarn,
Thanks.
> On Feb 12, 2018, at 2:43 PM, Piotr Zarzycki wrote:
>
> Let me build typedefs locally by Maven will see.
>
> 2018-02-12 13:36 GMT+01:00 Gabe Harbs :
>
>> I have no idea why this failed. The patch applied on my machine and line
>> 64
Let me build typedefs locally by Maven will see.
2018-02-12 13:36 GMT+01:00 Gabe Harbs :
> I have no idea why this failed. The patch applied on my machine and line
> 64 is an empty line.
>
> Maybe it’s a Windows line ending problem?
>
> Thoughts?
> Harbs
>
> > On Feb 12,
I have no idea why this failed. The patch applied on my machine and line 64 is
an empty line.
Maybe it’s a Windows line ending problem?
Thoughts?
Harbs
> On Feb 12, 2018, at 2:12 PM, apacheroyal...@gmail.com wrote:
>
> See
>
15 matches
Mail list logo