SZEDER Gábor e3371e9260 travis-ci: move setting environment variables to 'ci/lib-travisci.sh'
Our '.travis.yml's 'env.global' section sets a bunch of environment
variables for all build jobs, though none of them actually affects all
build jobs.  It's convenient for us, and in most cases it works just
fine, because irrelevant environment variables are simply ignored.

However, $GIT_SKIP_TESTS is an exception: it tells the test harness to
skip the two test scripts that are prone to occasional failures on
OSX, but as it's set for all build jobs those tests are not run in any
of the build jobs that are capable to run them reliably, either.

Therefore $GIT_SKIP_TESTS should only be set in the OSX build jobs,
but those build jobs are included in the build matrix implicitly (i.e.
by combining the matrix keys 'os' and 'compiler'), and there is no way
to set an environment variable only for a subset of those implicit
build jobs.  (Unless we were to add new scriptlets to '.travis.yml',
which is exactly the opposite direction that we took with commit
657343a60 (travis-ci: move Travis CI code into dedicated scripts,
2017-09-10)).

So move setting $GIT_SKIP_TESTS to 'ci/lib-travisci.sh', where it can
trivially be set only for the OSX build jobs.

Furthermore, move setting all other environment variables from
'.travis.yml' to 'ci/lib-travisci.sh', too, because a couple of
environment variables are already set there, and this way all
environment variables will be set in the same place.  All the logic
controlling our builds is already in the 'ci/*' scripts anyway, so
there is really no good reason to keep the environment variables
separately.

Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-12-12 12:58:27 -08:00
2017-07-17 14:54:53 -07:00
2017-08-23 14:36:03 -07:00
2017-07-10 14:24:36 -07:00
2017-07-06 18:14:44 -07:00
2017-03-24 13:31:01 -07:00
2017-06-27 10:35:49 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-03-13 15:28:54 -07:00
2017-06-24 14:28:41 -07:00
2017-07-31 13:05:15 -07:00
2017-05-25 13:08:23 +09:00
2017-05-08 15:12:57 +09:00
2017-05-08 15:12:57 +09:00
2017-06-24 14:28:41 -07:00
2017-05-29 12:34:43 +09:00
2017-05-02 10:46:41 +09:00
2017-07-17 14:54:56 -07:00
2016-05-09 12:29:08 -07:00
2017-01-25 14:42:37 -08:00
2017-07-17 14:54:56 -07:00
2017-05-29 12:34:43 +09:00
2017-06-22 14:15:20 -07:00
2017-08-04 12:40:37 -07:00
2016-05-09 12:29:08 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-06-19 12:38:44 -07:00
2017-06-22 14:15:21 -07:00
2016-05-09 12:29:08 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-03-31 08:33:56 -07:00
2017-05-29 12:34:43 +09:00
2017-03-31 08:33:56 -07:00
2016-07-01 12:44:57 -07:00
2016-07-01 12:44:57 -07:00
2017-08-23 14:36:03 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-07-12 15:18:23 -07:00
2017-06-24 14:28:41 -07:00
2017-01-30 14:17:00 -08:00
2017-06-24 14:28:41 -07:00
2016-12-07 11:31:59 -08:00
2017-06-24 14:28:41 -07:00
2017-06-27 10:35:49 -07:00
2016-07-29 11:05:07 -07:00
2016-07-29 11:05:07 -07:00
2017-07-17 14:54:56 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-02-08 15:39:55 -08:00
2017-01-30 14:17:00 -08:00
2017-05-29 12:34:43 +09:00
2017-06-24 14:28:41 -07:00
2017-06-30 13:11:54 -07:00
2017-08-04 12:40:37 -07:00
2017-06-27 10:35:49 -07:00
2016-07-28 11:26:03 -07:00
2016-07-28 11:26:03 -07:00
2017-05-29 12:34:43 +09:00
2017-07-17 14:54:56 -07:00
2017-07-17 14:54:56 -07:00
2017-06-27 10:35:49 -07:00
2017-08-23 14:36:03 -07:00
2017-06-24 14:28:41 -07:00
2016-04-25 15:17:15 -07:00
2017-06-27 10:35:49 -07:00
2017-03-31 08:33:56 -07:00
2017-06-13 13:47:09 -07:00
2017-07-12 15:18:23 -07:00
2017-03-31 08:33:56 -07:00
2017-05-22 10:20:46 +09:00
2017-05-22 10:20:46 +09:00
2017-07-12 15:18:23 -07:00
2017-06-24 14:28:41 -07:00
2017-07-17 14:54:56 -07:00
2017-05-29 12:34:43 +09:00
2017-05-29 12:34:43 +09:00
2016-08-05 09:28:17 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2016-09-26 18:16:23 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -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.

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 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%