On Sun, Apr 1, 2018, 8:10 PM Lars Schneider wrote:
>
> That's a good summary and I don't see a better solution. While (3)
> sounds nice, I think (2) is the fastest/most pragmatic solution.
>
> We already use the Travis cache [1]. You could use that mechanism to
> store
I'm extremely sorry, I forgot to attach my travis-ci job build with my
previous message. Here it is :
https://travis-ci.org/SiddharthaMishra/git/jobs/349478746#L1204.
I also apologize for not trimming the email properly in the previous message.
Sorry for the inconvenience,
Siddhartha
On Mon, Mar 12, 2018 at 3:49 PM, Lars Schneider
wrote:
> Hi,
>
> That looks interesting but I agree with Dscho that we should not limit
> this to master/maint.
>
> I assume you did run this on TravisCI already? Can you share a link?
> I assume you did find errors? Can we
On Tue, Mar 6, 2018 at 6:57 AM, Junio C Hamano wrote:
> SiddharthaMishra writes:
>
>> Added a job to run clang static code analysis on the master and maint branch
>>
>> Signed-off-by: SiddharthaMishra
>> ---
>
> Why on 'master' and
4 matches
Mail list logo