Elijah Newren c641ca6707 merge-recursive: handle addition of submodule on our side of history
The code for a newly added path assumed that the path was a normal file,
and thus checked for there being a directory still being in the way of
the file.  Note that since unpack_trees() does path-in-the-way checks
already, the only way for there to be a directory in the way at this
point in the code, is if there is some kind of D/F conflict in the merge.

For a submodule addition on HEAD's side of history, the submodule would
have already been present.  This means that we do expect there to be a
directory present but should not consider it to be "in the way"; instead,
it's the expected submodule.  So, when there's a submodule addition from
HEAD's side, don't bother checking the working copy for a directory in
the way.

Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-11-15 12:42:34 +09:00
2017-07-10 14:24:36 -07:00
2017-09-10 17:08:22 +09:00
2017-10-29 10:04:12 +08:00
2017-10-26 12:29:23 +09:00
2017-07-06 18:14:44 -07:00
2017-09-10 17:08:22 +09: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-02-22 14:50:32 -08:00
2016-02-22 14:50:32 -08:00
2017-03-13 15:28:54 -07:00
2017-09-29 11:23:43 +09: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-08-03 11:08:10 -07:00
2017-05-02 10:46:41 +09:00
2017-10-03 15:42:49 +09:00
2016-05-09 12:29:08 -07:00
2017-01-25 14:42:37 -08:00
2017-09-29 11:23:43 +09:00
2017-09-06 13:11:25 +09:00
2017-10-03 15:42:48 +09:00
2017-06-22 14:15:20 -07:00
2016-05-09 12:29:08 -07:00
2017-06-24 14:28:41 -07:00
2015-11-20 08:02:05 -05:00
2017-06-22 14:15:21 -07:00
2016-05-09 12:29:08 -07:00
2017-10-01 17:18:03 +09:00
2017-03-31 08:33:56 -07: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-10-30 14:00:44 +09:00
2017-10-03 15:42:49 +09:00
2017-10-07 16:27:54 +09:00
2017-08-23 15:12:07 -07:00
2017-06-24 14:28:41 -07:00
2016-02-22 14:51:09 -08:00
2017-01-30 14:17:00 -08:00
2017-09-06 17:19:54 +09:00
2017-10-11 14:52:22 +09:00
2016-07-29 11:05:07 -07:00
2016-07-29 11:05:07 -07:00
2017-06-24 14:28:41 -07:00
2017-09-19 10:47:52 +09:00
2017-10-01 17:18:03 +09:00
2017-10-01 17:18:03 +09:00
2017-10-01 17:18:03 +09:00
2017-10-01 17:18:03 +09:00
2017-09-29 11:23:43 +09:00
2017-01-30 14:17:00 -08:00
2017-08-23 15:12:07 -07:00
2017-08-22 10:29:03 -07:00
2017-05-29 12:34:43 +09:00
2017-10-28 10:18:40 +09:00
2016-07-28 11:26:03 -07:00
2017-09-28 14:47:53 +09:00
2017-10-03 15:42:48 +09:00
2017-10-18 14:24:09 +09:00
2017-10-02 13:15:59 +09:00
2017-09-25 15:24:06 +09:00
2016-04-25 15:17:15 -07:00
2017-09-29 11:23:42 +09:00
2017-09-29 11:23:43 +09:00
2017-10-03 08:42:57 +09:00
2017-03-31 08:33:56 -07:00
2017-10-18 10:19:07 +09:00
2017-03-31 08:33:56 -07:00
2017-09-29 11:23:43 +09:00
2017-06-24 14:28:41 -07:00
2017-09-28 14:47:52 +09:00
2016-08-05 09:28:17 -07:00
2017-08-26 22:55:04 -07:00
2017-09-29 11:23:42 +09:00
2017-06-24 14:28:41 -07:00
2017-09-29 11:23:43 +09:00
2016-02-22 10:40:35 -08: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 582 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%