Junio C Hamano a93dcb0a56 Merge branch 'bw/submodule-is-active'
"what URL do we want to update this submodule?" and "are we
interested in this submodule?" are split into two distinct
concepts, and then the way used to express the latter got extended,
paving a way to make it easier to manage a project with many
submodules and make it possible to later extend use of multiple
worktrees for a project with submodules.

* bw/submodule-is-active:
  submodule add: respect submodule.active and submodule.<name>.active
  submodule--helper init: set submodule.<name>.active
  clone: teach --recurse-submodules to optionally take a pathspec
  submodule init: initialize active submodules
  submodule: decouple url and submodule interest
  submodule--helper clone: check for configured submodules using helper
  submodule sync: use submodule--helper is-active
  submodule sync: skip work for inactive submodules
  submodule status: use submodule--helper is-active
  submodule--helper: add is-active subcommand
2017-03-30 14:07:14 -07:00
2017-03-06 11:19:09 -08:00
2017-02-16 14:45:13 -08:00
2017-03-17 13:50:25 -07:00
2017-03-26 15:34:44 -07:00
2017-03-30 14:07:14 -07:00
2017-03-24 13:31:01 -07:00
2017-03-06 11:19:09 -08:00
2016-11-22 13:55:20 -08:00
2017-03-13 15:28:54 -07:00
2017-03-13 15:28:54 -07:00
2017-03-28 14:06:00 -07:00
2017-01-25 14:42:37 -08:00
2017-03-10 13:24:24 -08:00
2016-10-27 14:58:50 -07:00
2016-12-12 15:15:07 -08:00
2017-02-16 14:45:12 -08:00
2016-12-19 14:45:35 -08:00
2017-03-24 12:59:15 -07:00
2017-02-15 12:54:19 -08:00
2017-03-17 12:18:41 -07:00
2017-03-17 10:40:25 -07:00
2017-03-22 13:41:41 -07:00
2017-03-22 13:41:41 -07:00
2017-02-20 01:11:26 -08:00
2017-01-30 14:17:00 -08:00
2016-12-07 11:31:59 -08:00
2017-03-28 14:06:00 -07:00
2016-12-07 11:31:59 -08:00
2017-01-30 14:17:00 -08:00
2017-02-08 15:39:55 -08:00
2017-02-08 15:39:55 -08:00
2017-01-30 14:17:00 -08:00
2017-03-28 14:05:59 -07:00
2017-03-13 14:39:36 -07:00
2017-03-10 13:24:24 -08:00
2017-01-30 14:17:00 -08:00
2017-03-17 13:50:25 -07:00
2017-03-28 13:54:14 -07:00
2017-03-22 15:41:21 -07:00
2017-03-17 13:50:25 -07:00
2017-03-23 11:19:23 -07:00
2017-03-17 13:50:25 -07:00
2017-02-27 11:02:06 -08:00
2017-01-31 13:14:56 -08: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 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%