1
0
mirror of https://github.com/git/git.git synced 2025-04-12 11:02:43 +00:00
Nguyễn Thái Ngọc Duy c041d54a74 cache-tree.c: fix i-t-a entry skipping directory updates sometimes
Commit 3cf773e (cache-tree: fix writing cache-tree when CE_REMOVE is
present - 2012-12-16) skips i-t-a entries when building trees objects
from the index. Unfortunately it may skip too much.

The code in question checks if an entry is an i-t-a one, then no tree
entry will be written. But it does not take into account that
directories can also be written with the same code. Suppose we have
this in the index.

    a-file
    subdir/file1
    subdir/file2
    subdir/file3
    the-last-file

We write an entry for a-file as normal and move on to subdir/file1,
where we realize the entry name for this level is simply just
"subdir", write down an entry for "subdir" then jump three items ahead
to the-last-file.

That is what happens normally when the first file in subdir is not an
i-t-a entry. If subdir/file1 is an i-t-a, because of the broken
condition in this code, we still think "subdir" is an i-t-a file and
not writing "subdir" down and jump to the-last-file. The result tree
now only has two items: a-file and the-last-file. subdir should be
there too (even though it only records two sub-entries, file2 and
file3).

If the i-t-a entry is subdir/file2 or subdir/file3, this is not a
problem because we jump over them anyway. Which may explain why the
bug is hidden for nearly four years.

Fix it by making sure we only skip i-t-a entries when the entry in
question is actual an index entry, not a directory.

Reported-by: Yuri Kanivetsky <yuri.kanivetsky@gmail.com>
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-07-18 13:45:33 -07:00
2016-05-10 11:19:07 -07:00
2016-06-13 10:42:13 -07:00
2016-02-22 14:51:09 -08:00
2016-05-17 14:38:20 -07:00
2016-06-12 01:25:58 +09:00
2016-04-25 15:17:15 -07:00
2016-05-09 12:29:08 -07:00
2016-02-22 14:51:09 -08:00
2016-02-22 14:50:32 -08:00
2016-02-22 14:50:32 -08:00
2015-10-05 12:30:19 -07:00
2016-05-09 12:29:08 -07:00
2016-02-22 14:51:09 -08:00
2015-08-03 11:01:21 -07:00
2016-05-09 12:29:08 -07:00
2016-01-18 19:48:43 -08:00
2016-05-09 12:29:08 -07: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
2016-04-03 10:29:22 -07:00
2015-09-28 14:57:10 -07:00
2016-05-23 14:54:29 -07:00
2016-05-23 14:54:29 -07:00
2016-05-09 12:29:08 -07:00
2016-05-09 12:29:08 -07:00
2016-05-17 14:38:34 -07:00
2015-06-29 11:39:10 -07:00
2016-05-10 13:40:29 -07:00
2016-06-13 10:42:13 -07:00
2016-05-17 14:38:28 -07:00
2016-02-22 14:51:09 -08:00
2016-05-09 12:29:08 -07:00
2016-05-06 14:45:44 -07:00
2016-02-22 14:51:09 -08:00
2016-05-17 14:38:32 -07:00
2016-05-17 14:38:28 -07:00
2016-05-06 14:45:44 -07: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
2015-11-20 08:02:05 -05:00
2016-05-26 13:17:21 -07:00
2016-03-01 12:24:15 -08:00
2016-03-01 12:24:15 -08:00
2016-05-09 12:29:08 -07:00
2015-09-25 08:54:54 -07:00
2016-06-06 14:29:32 -07:00
2016-05-23 14:54:38 -07:00
2016-04-25 15:17:15 -07:00
2016-05-06 14:45:44 -07:00
2016-05-09 12:29:08 -07:00
2016-05-09 12:29:08 -07:00
2016-05-06 14:45:44 -07:00
2016-05-17 14:38:28 -07:00
2016-05-17 14:38:28 -07:00
2016-02-22 10:40:35 -08:00
2016-05-17 14:38: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 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-.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
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Readme 829 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.2%
Python 0.8%
Other 2.1%