git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Lars Schneider <larsxschneider@gmail.com>
To: "Johannes Schindelin" <johannes.schindelin@gmx.de>,
	"Дилян Палаузов" <dilyan.palauzov@aegee.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git and the Clang Static Analyzer
Date: Mon, 8 May 2017 17:45:38 +0100	[thread overview]
Message-ID: <C925C220-DD28-41A0-BF72-F8A906BB460D@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1705081250550.146734@virtualbox>


> On 08 May 2017, at 12:12, Johannes Schindelin <johannes.schindelin@gmx.de> wrote:
> 
> Hi Dilyan,
> 
> 
> On Sun, 7 May 2017, Дилян Палаузов wrote:
> 
>> ...
> 
> Also: to make it *really* useful for other developers, it would be a good
> idea for you to try your hand at patching the .travis.yml file in such a
> way that the static analysis is performed as part of the Continuous
> Testing, and to contribute said patch. That way, other contributors could
> not only see how it is done (and copy-paste the commands, including `apt
> install` calls insofar necessary), but also to see the reports on a
> trusted website (Travis').

I did that here:
https://github.com/larsxschneider/git/commit/faf4ecfdca1a732459c1f93c334928ee2826d490

Unfortunately, there are still too many issues to activate this job:
https://travis-ci.org/larsxschneider/git/jobs/205507241

See this thread for more info:
http://public-inbox.org/git/BAB1EE0E-B258-4108-AE24-110172086DE4@gmail.com/

- Lars

  reply	other threads:[~2017-05-08 16:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-07 11:50 git and the Clang Static Analyzer Дилян Палаузов
2017-05-08 11:12 ` Johannes Schindelin
2017-05-08 16:45   ` Lars Schneider [this message]
2017-05-08 19:26   ` Дилян Палаузов
2017-05-08 20:18     ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C925C220-DD28-41A0-BF72-F8A906BB460D@gmail.com \
    --to=larsxschneider@gmail.com \
    --cc=dilyan.palauzov@aegee.org \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).