Nguyễn Thái Ngọc Duy c7f3259d0d unpack-trees: avoid the_index in verify_absent()
Both functions that are updated in this commit are called by
verify_absent(), which is part of the "unpack-trees" operation that is
supposed to work on any index file specified by the caller. Thanks to
Brandon [1] [2], an implicit dependency on the_index is exposed. This
commit fixes it.

In both functions, it makes sense to use src_index to check for
exclusion because it's almost unchanged and should give us the same
outcome as if running the exclude check before the unpack.

It's "almost unchanged" because we do invalidate cache-tree and
untracked cache in the source index. But this should not affect how
exclude machinery uses the index: to see if a file is tracked, and to
read a blob from the index instead of worktree if it's marked
skip-worktree (i.e. it's not available in worktree)

[1] a0bba65b10 (dir: convert is_excluded to take an index - 2017-05-05
[2] 2c1eb10454 (dir: convert read_directory to take an index - 2017-05-05)

Helped-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-08-13 14:14:43 -07:00
2018-05-30 14:04:08 +09:00
2018-07-24 14:50:50 -07:00
2018-08-02 15:38:09 -07:00
2018-06-19 02:19:42 +09:00
2018-06-25 13:22:39 -07:00
2018-06-25 13:22:38 -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
2018-03-30 12:49:57 -07:00
2018-03-30 12:49:57 -07:00
2018-05-30 14:04:07 +09:00
2018-08-02 15:30:42 -07:00
2018-05-08 15:59:17 +09:00
2018-06-01 15:06:37 +09:00
2017-12-08 09:16:27 -08:00
2017-12-08 09:16:27 -08:00
2018-05-08 15:59:34 +09:00
2018-05-08 15:59:17 +09: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
2018-06-19 09:34:32 -07:00
2018-06-25 13:22:27 -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-09-06 17:19:54 +09:00
2018-08-02 15:30:45 -07:00
2018-07-18 12:20:28 -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-05-30 14:04:07 +09:00
2018-08-02 15:30:42 -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-02 15:30:42 -07:00
2018-05-08 15:59:21 +09:00
2018-06-28 12:53:29 -07: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-03-15 12:01:08 -07:00
2018-06-01 15:06:37 +09:00
2018-04-24 11:12:32 +09:00
2017-10-07 16:27:54 +09:00
2006-03-25 16:35:43 -08: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-02 15:30:43 -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-07-09 14:38:12 -07:00
2018-05-29 17:10:05 +09: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
Git with broken hash generation to generate collisions between object IDs. Don't use this!
https://undefinedbehavior.de/posts/commit-vandalism/
Readme 217 MiB
Languages
C 50%
Shell 38.2%
Perl 5.5%
Tcl 3.5%
Python 0.9%
Other 1.7%