Jeff King 577dd0d29b mark_parents_uninteresting(): drop missing object check
We allow UNINTERESTING objects in a traversal to be
unavailable. As part of this, mark_parents_uninteresting()
checks whether we have a particular uninteresting parent; if
not, we will mark it as "parsed" so that later code skips
it.

This code is redundant and even a little bit harmful, so
let's drop it.

It's redundant because when our parse_object() call in
add_parents_to_list() fails, we already quietly skip
UNINTERESTING parents. This redundancy is a historical
artifact. The mark_parents_uninteresting() protection is
from 454fbbcde3 (git-rev-list: allow missing objects when
the parent is marked UNINTERESTING, 2005-07-10). Much later,
aeeae1b771 (revision traversal: allow UNINTERESTING objects
to be missing, 2009-01-27) covered more cases by making the
actual parse more gentle.

  As an aside, even if this weren't redundant, it would be
  insufficient. The gentle parsing handles both missing and
  corrupted objects, whereas the has_object_file() check
  we're getting rid of covers only missing ones.

And the code we're dropping is harmful for two reasons:

  1. We spend extra time on the object lookup, even though
     we don't actually need the information at this point
     (and will just repeat that lookup later when we parse
     for the common case that we _do_ have the object).

  2. It "lies" about the commit by setting the parsed flag,
     even though we didn't load any useful data into the
     struct. This shouldn't matter for the UNINTERESTING
     case, but we may later clear our flags and do another
     traversal in the same process. While pretty unlikely,
     it's possible that we could then look at the same
     commit without the UNINTERESTING flag, in which case
     we'd produce the wrong result (we'd think it's a commit
     with no parents, when in fact we should probably die
     due to the missing object).

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-05-13 11:08:58 +09:00
2018-03-15 15:00:46 -07:00
2017-07-06 18:14:44 -07:00
2018-03-28 11:04:24 -07:00
2018-03-14 12:01:07 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-11-15 12:14:28 +09:00
2018-03-06 14:54:07 -08: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-12-27 11:16:25 -08:00
2017-12-27 11:16:25 -08:00
2017-08-03 11:08:10 -07:00
2018-03-06 14:54:07 -08:00
2017-05-02 10:46:41 +09:00
2018-02-13 10:17:12 -08:00
2018-02-13 10:17:12 -08:00
2017-10-24 10:19:06 +09:00
2018-03-06 14:54:07 -08:00
2018-03-06 14:54:07 -08:00
2018-02-13 13:39:08 -08:00
2018-02-13 13:39:04 -08:00
2018-02-15 14:55:43 -08:00
2017-06-24 14:28:41 -07:00
2018-02-02 11:28:41 -08:00
2018-02-02 11:28:41 -08:00
2017-12-08 09:16:27 -08:00
2017-12-08 09:16:27 -08:00
2018-03-06 14:54:07 -08:00
2018-02-15 14:55:43 -08:00
2018-02-22 10:08:05 -08:00
2018-03-06 14:54:07 -08:00
2018-04-02 10:13:35 -07:00
2018-02-13 10:17:12 -08:00
2017-11-21 14:05:30 +09:00
2018-03-06 14:54:07 -08:00
2018-03-21 11:30:12 -07:00
2017-06-24 14:28:41 -07:00
2018-02-22 10:08:05 -08:00
2018-02-22 10:08:05 -08:00
2017-09-06 17:19:54 +09:00
2018-03-06 14:54:07 -08:00
2018-03-15 15:00:46 -07:00
2018-03-06 14:54:07 -08:00
2017-12-27 12:28:06 -08:00
2017-11-22 14:11:56 +09:00
2018-03-06 14:54:07 -08:00
2018-02-02 11:28:41 -08:00
2018-03-06 14:54:07 -08: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
2017-12-13 11:14:25 -08:00
2017-12-06 09:23:44 -08:00
2017-10-17 10:51:29 +09: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-03-22 14:24:45 -07:00
2018-01-22 11:32:51 -08:00
2018-02-27 10:33:58 -08:00
2018-03-21 11:30:10 -07:00
2017-09-29 11:23:43 +09:00
2018-03-06 14:54:07 -08:00
2018-03-14 12:01:05 -07:00
2018-02-22 10:08:05 -08:00
2018-02-22 10:08:05 -08:00
2018-02-22 10:08:05 -08:00
2017-08-26 22:55:04 -07:00
2018-02-13 13:39:04 -08:00
2018-02-13 13:39:04 -08:00
2017-06-24 14:28:41 -07:00
2018-03-29 15:39:59 -07:00
2018-03-29 15:39:59 -07:00
2018-02-22 10:08:05 -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 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 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%