Junio C Hamano ee30f17805 Merge branch 'sb/submodule-path-misc-bugs' into sb/submodule-init
"git submodule" reports the paths of submodules the command
recurses into, but this was incorrect when the command was not run
from the root level of the superproject.

Any further comments?  Otherwise will merge to 'next'.

* sb/submodule-path-misc-bugs: (600 commits)
  t7407: make expectation as clear as possible
  submodule update: test recursive path reporting from subdirectory
  submodule update: align reporting path for custom command execution
  submodule status: correct path handling in recursive submodules
  submodule update --init: correct path handling in recursive submodules
  submodule foreach: correct path display in recursive submodules
  Git 2.8
  Documentation: fix git-p4 AsciiDoc formatting
  mingw: skip some tests in t9115 due to file name issues
  t1300: fix the new --show-origin tests on Windows
  t1300-repo-config: make it resilient to being run via 'sh -x'
  config --show-origin: report paths with forward slashes
  submodule: fix regression for deinit without submodules
  l10n: pt_PT: Update and add new translations
  l10n: ca.po: update translation
  Git 2.8-rc4
  Documentation: fix broken linkgit to git-config
  Documentation: use ASCII quotation marks in git-p4
  Revert "config.mak.uname: use clang for Mac OS X 10.6"
  git-compat-util: st_add4: work around gcc 4.2.x compiler crash
  ...
2016-04-14 12:47:45 -07:00
2016-02-22 14:51:09 -08:00
2016-03-15 01:35:39 +00:00
2016-02-26 13:37:16 -08:00
2016-02-22 14:51:09 -08:00
2014-07-28 10:14:33 -07:00
2016-02-22 14:50:32 -08:00
2016-02-22 14:50:32 -08:00
2016-02-26 13:37:16 -08:00
2015-10-05 12:30:19 -07:00
2015-11-20 08:02:05 -05:00
2016-02-22 14:51:09 -08:00
2015-08-03 11:01:21 -07:00
2015-08-03 11:01:27 -07:00
2016-03-16 13:16:54 -07:00
2016-02-26 13:37:23 -08:00
2016-01-18 19:48:43 -08:00
2014-12-12 14:31:42 -08:00
2016-02-26 13:37:16 -08:00
2015-11-20 08:02:05 -05:00
2014-03-31 15:29:27 -07:00
2015-11-20 08:02:05 -05:00
2016-03-17 11:26:18 -07:00
2015-09-28 14:57:10 -07:00
2016-02-22 14:51:09 -08:00
2016-02-10 14:20:06 -08:00
2016-02-26 13:37:16 -08:00
2014-01-17 12:21:20 -08:00
2016-02-22 14:51:09 -08:00
2015-06-29 11:39:10 -07:00
2016-03-28 12:19:45 -07:00
2016-02-22 14:51:09 -08:00
2016-02-22 14:51:09 -08:00
2014-07-07 13:56:38 -07:00
2013-05-08 15:31:54 -07:00
2016-03-10 10:56:43 -08:00
2016-02-24 13:25:54 -08:00
2016-02-17 10:13:31 -08:00
2016-02-22 14:51:09 -08:00
2014-10-20 12:23:48 -07:00
2015-09-25 10:18:18 -07:00
2016-03-16 13:16:54 -07:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2016-02-26 13:37:16 -08:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2014-03-31 15:29:27 -07:00
2015-11-20 08:02:05 -05:00
2015-09-25 08:54:54 -07:00
2016-03-17 11:32:13 -07:00
2016-02-17 10:13:33 -08:00
2015-10-05 12:30:05 -07:00
2016-02-26 13:37:16 -08:00
2014-06-13 11:49:40 -07:00
2014-12-22 12:27:30 -08:00
2014-12-22 12:27:30 -08:00
2015-11-20 08:02:05 -05:00
2014-03-31 15:29:27 -07:00
2016-01-27 14:27:19 -08:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2014-09-02 13:28:44 -07:00
2015-11-20 08:02:05 -05:00
2015-08-11 14:29:36 -07:00
2016-02-22 10:40:35 -08:00
2016-01-19 11:22:29 -08:00
2016-02-26 13:37:16 -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 http://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-commandname.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 http://news.gmane.org/gmane.comp.version-control.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 611 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%