Ramsay Jones fb16287719 fsck: check skiplist for object in fsck_blob()
Since commit ed8b10f631 ("fsck: check .gitmodules content", 2018-05-02),
fsck will issue an error message for '.gitmodules' content that cannot
be parsed correctly. This is the case, even when the corresponding blob
object has been included on the skiplist. For example, using the cgit
repository, we see the following:

  $ git fsck
  Checking object directories: 100% (256/256), done.
  error: bad config line 5 in blob .gitmodules
  error in blob 51dd1eff1edc663674df9ab85d2786a40f7ae3a5: gitmodulesParse: could not parse gitmodules blob
  Checking objects: 100% (6626/6626), done.
  $

  $ git config fsck.skiplist '.git/skip'
  $ echo 51dd1eff1edc663674df9ab85d2786a40f7ae3a5 >.git/skip
  $

  $ git fsck
  Checking object directories: 100% (256/256), done.
  error: bad config line 5 in blob .gitmodules
  Checking objects: 100% (6626/6626), done.
  $

Note that the error message issued by the config parser is still
present, despite adding the object-id of the blob to the skiplist.

One solution would be to provide a means of suppressing the messages
issued by the config parser. However, given that (logically) we are
asking fsck to ignore this object, a simpler approach is to just not
call the config parser if the object is to be skipped. Add a check to
the 'fsck_blob()' processing function, to determine if the object is
on the skiplist and, if so, exit the function early.

Signed-off-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-07-03 09:49:44 -07:00
2018-03-15 15:00:46 -07:00
2017-07-06 18:14:44 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2017-03-13 15:28:54 -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
2017-01-25 14:42:37 -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-05-21 23:55:12 -04: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-01-30 14:17:00 -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-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
2017-03-31 08:33:56 -07:00
2018-02-27 10:33:58 -08:00
2018-05-21 23:55:12 -04:00
2017-03-31 08:33:56 -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-05-21 23:50:11 -04: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 559 MiB
Languages
C 50.4%
Shell 38.9%
Perl 4.3%
Tcl 3.1%
Python 0.8%
Other 2.3%