SZEDER Gábor 0860a7641b travis-ci: fail if Coccinelle static analysis found something to transform
Coccinelle's and in turn 'make coccicheck's exit code only indicates
that Coccinelle managed to finish its analysis without any errors
(e.g. no unknown --options, no missing files, no syntax errors in the
semantic patches, etc.), but it doesn't indicate whether it found any
undesired code patterns to transform or not.  To find out the latter,
one has to look closer at 'make coccicheck's standard output and look
for lines like:

  SPATCH result: contrib/coccinelle/<something>.cocci.patch

And this only indicates that there is something to transform, but to
see what the suggested transformations are one has to actually look
into those '*.cocci.patch' files.

This makes the automated static analysis build job on Travis CI not
particularly useful, because it neither draws our attention to
Coccinelle's findings, nor shows the actual findings.  Consequently,
new topics introducing undesired code patterns graduated to master
on several occasions without anyone noticing.

The only way to draw attention in such an automated setting is to fail
the build job.  Therefore, modify the 'ci/run-static-analysis.sh'
build script to check all the resulting '*.cocci.patch' files, and
fail the build job if any of them turns out to be not empty.  Include
those files' contents, i.e. Coccinelle's suggested transformations, in
the build job's trace log, so we'll know why it failed.

Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-07-23 12:08:38 -07:00
2018-07-18 12:20:31 -07:00
2018-07-18 12:24:17 -07:00
2018-06-19 02:19:42 +09:00
2018-07-18 12:20:33 -07:00
2018-06-25 13:22:39 -07:00
2018-06-25 13:22:38 -07:00
2018-07-18 12:20:28 -07:00
2018-05-29 12:42:30 +09:00
2018-07-18 12:20:28 -07:00
2018-07-18 12:20:28 -07:00
2018-06-25 13:22:37 -07:00
2018-07-18 12:20:28 -07:00
2018-07-18 12:20:28 -07:00
2018-03-30 12:49:57 -07:00
2018-03-30 12:49:57 -07:00
2018-05-30 14:04:07 +09:00
2018-07-18 12:20:28 -07:00
2018-07-18 12:20:28 -07:00
2018-05-08 15:59:17 +09:00
2018-06-01 15:06:37 +09:00
2018-05-08 15:59:22 +09:00
2018-07-18 12:20:28 -07:00
2018-07-18 12:20:34 -07:00
2018-05-30 14:04:10 +09:00
2018-05-08 15:59:34 +09:00
2018-05-08 15:59:17 +09:00
2018-05-08 15:59:16 +09:00
2018-07-18 12:20:28 -07:00
2018-05-21 23:55:12 -04:00
2018-05-08 15:59:34 +09:00
2018-06-19 09:34:32 -07:00
2018-06-25 13:22:27 -07:00
2018-07-18 12:20:28 -07:00
2018-07-18 12:20:31 -07:00
2018-07-18 12:20:31 -07:00
2018-06-01 15:06:37 +09:00
2018-05-08 15:59:16 +09:00
2018-04-11 13:09:55 +09:00
2018-05-30 21:51:28 +09:00
2018-05-23 14:38:13 +09:00
2018-07-18 12:20:28 -07:00
2018-07-18 12:20:28 -07:00
2018-06-21 12:22:48 -07:00
2018-06-21 12:22:48 -07:00
2018-05-30 14:04:07 +09:00
2018-06-01 15:06:37 +09:00
2018-07-18 12:20:28 -07:00
2018-05-30 14:04:07 +09:00
2018-05-23 14:38:13 +09:00
2018-07-18 12:20:28 -07:00
2018-05-08 15:59:21 +09:00
2018-06-28 12:53:29 -07:00
2018-06-25 13:22:27 -07:00
2018-07-18 12:20:28 -07:00
2018-07-18 12:20:28 -07:00
2018-05-30 14:04:11 +09:00
2018-06-01 15:06:37 +09:00
2018-04-24 11:12:32 +09:00
2018-05-30 14:04:07 +09:00
2018-03-30 12:49:57 -07:00
2018-03-30 12:49:57 -07:00
2018-07-18 12:20:28 -07:00
2018-05-30 21:51:28 +09:00
2018-05-29 17:10:05 +09:00
2018-05-29 17:10:05 +09:00
2018-07-18 12:20:28 -07:00

Git - fast, scalable, distributed revision control system

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals.

Git is an Open Source project covered by the GNU General Public License version 2 (some parts of it are under different licenses, compatible with the GPLv2). It was originally written by Linus Torvalds with help of a group of hackers around the net.

Please read the file INSTALL for installation instructions.

Many Git online resources are accessible from https://git-scm.com/ including full documentation and Git related tools.

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.txt for a useful minimum set of commands, and Documentation/git-.txt for documentation of each command. If git has been correctly installed, then the tutorial can also be read with man gittutorial or git help tutorial, and the documentation of each command with man git-<commandname> or git help <commandname>.

CVS users may also want to read Documentation/gitcvs-migration.txt (man gitcvs-migration or git help cvs-migration if git is installed).

The user discussion and development of Git take place on the Git mailing list -- everyone is welcome to post bug reports, feature requests, comments and patches to git@vger.kernel.org (read Documentation/SubmittingPatches for instructions on patch submission). To subscribe to the list, send an email with just "subscribe git" in the body to majordomo@vger.kernel.org. The mailing list archives are available at https://public-inbox.org/git/, http://marc.info/?l=git and other archival sites.

Issues which are security relevant should be disclosed privately to the Git Security mailing list git-security@googlegroups.com.

The maintainer frequently sends the "What's cooking" reports that list the current status of various development topics to the mailing list. The discussion following them give a good reference for project status, development direction and remaining tasks.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (depending on your mood):

  • random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronunciation of "get" may or may not be relevant.
  • stupid. contemptible and despicable. simple. Take your pick from the dictionary of slang.
  • "global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room.
  • "goddamn idiotic truckload of sh*t": when it breaks
Description
No description provided
Readme 638 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%