Junio C Hamano e4095da40e Merge branch 'en/merge-recursive-skip-fix'
When the sparse checkout feature is in use, "git cherry-pick" and
other mergy operations lost the skip_worktree bit when a path that
is excluded from checkout requires content level merge, which is
resolved as the same as the HEAD version, without materializing the
merge result in the working tree, which made the path appear as
deleted.  This has been corrected by preserving the skip_worktree
bit (and not materializing the file in the working tree).

* en/merge-recursive-skip-fix:
  merge-recursive: preserve skip_worktree bit when necessary
  t3507: add a testcase showing failure with sparse checkout
2018-08-15 15:08:26 -07:00
2018-07-24 14:50:50 -07:00
2018-08-15 15:08:23 -07:00
2018-06-19 02:19:42 +09:00
2018-08-15 15:08:25 -07:00
2017-07-06 18:14:44 -07:00
2018-06-25 13:22:39 -07:00
2018-06-25 13:22:38 -07:00
2018-05-29 12:42:30 +09:00
2018-08-15 15:08:23 -07:00
2018-08-15 15:08:23 -07:00
2017-03-13 15:28:54 -07:00
2017-11-15 12:14:28 +09:00
2018-07-18 12:20:28 -07:00
2017-12-27 11:16:25 -08:00
2018-06-25 13:22:37 -07:00
2018-07-18 12:20:28 -07:00
2017-05-02 10:46:41 +09:00
2018-03-30 12:49:57 -07:00
2018-03-30 12:49:57 -07:00
2016-05-09 12:29:08 -07:00
2018-05-30 14:04:07 +09:00
2018-08-15 15:08:23 -07:00
2018-08-02 15:30:42 -07:00
2018-05-08 15:59:17 +09:00
2018-08-15 15:08:23 -07:00
2018-08-15 15:08:25 -07:00
2018-05-08 15:59:22 +09:00
2016-05-09 12:29:08 -07:00
2017-12-08 09:16:27 -08:00
2017-12-08 09:16:27 -08:00
2018-08-15 15:08:23 -07:00
2018-08-02 15:30:40 -07:00
2018-08-15 15:08:23 -07:00
2018-05-30 14:04:10 +09:00
2018-08-15 15:08:23 -07:00
2018-05-08 15:59:17 +09:00
2018-08-15 15:08:20 -07:00
2018-08-02 15:30:43 -07:00
2018-08-02 15:30:42 -07:00
2018-05-21 23:55:12 -04:00
2018-05-08 15:59:34 +09:00
2016-07-01 12:44:57 -07:00
2018-06-19 09:34:32 -07:00
2018-06-25 13:22:27 -07:00
2018-08-15 15:08:23 -07:00
2018-08-02 15:30:44 -07:00
2018-08-02 15:30:44 -07:00
2018-06-01 15:06:37 +09:00
2018-07-16 14:27:39 -07:00
2018-04-11 13:09:55 +09:00
2018-05-30 21:51:28 +09:00
2017-06-24 14:28:41 -07:00
2017-09-06 17:19:54 +09:00
2018-08-15 15:08:25 -07:00
2018-08-02 15:30:45 -07:00
2018-08-15 15:08:23 -07:00
2018-08-02 15:30:42 -07:00
2017-12-27 12:28:06 -08:00
2017-11-22 14:11:56 +09: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-02-02 11:28:41 -08:00
2018-06-01 15:06:37 +09:00
2018-07-18 12:20:28 -07:00
2018-07-24 14:50:47 -07:00
2018-08-15 15:08:25 -07:00
2017-12-12 10:41:15 -08:00
2017-12-19 11:33:55 -08:00
2018-01-16 12:16:54 -08:00
2018-08-15 15:08:23 -07:00
2018-08-15 15:08:23 -07:00
2018-05-08 15:59:21 +09:00
2018-06-25 13:22:27 -07:00
2018-08-02 15:30:42 -07:00
2018-06-28 09:33:30 -07:00
2018-08-15 15:08:23 -07:00
2018-07-18 12:20:28 -07:00
2017-03-31 08:33:56 -07:00
2018-08-15 15:08:23 -07:00
2018-03-15 12:01:08 -07:00
2018-08-15 15:08:23 -07:00
2018-06-01 15:06:37 +09:00
2018-04-24 11:12:32 +09:00
2018-08-15 15:08:25 -07:00
2018-03-30 12:49:57 -07:00
2018-03-30 12:49:57 -07:00
2017-08-26 22:55:04 -07:00
2018-08-15 15:08:23 -07:00
2018-08-15 15:08:23 -07:00
2018-08-02 15:30:43 -07:00
2018-08-02 15:30:39 -07:00
2018-05-30 21:51:28 +09:00
2018-08-15 15:08:25 -07: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 582 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%