Patrick Steinhardt 47ef2193b3 odb/source-packed: flag known-bad objects as corrupt and not missing
When reading packed objects we know to tell apart missing objects and
corrupt objects by returning a positive error code in the former case,
and a negative one in the latter case. We do that by distinguishing
between errors returned by `find_pack_entry()`, which yields the offset
of the object, and `packed_object_info()`, which reads the object
contents.

But even though we already distinguish those cases when reading packed
objects, the logic is broken in case a caller tries to read an object
that has been marked as corrupt. In that case, `find_pack_entry()` will
tell us that the object in question does not exist, and consequently
we'll not flag the object as corrupt but as missing.

Fix this issue by bubbling up whether the object is corrupt and, if so,
which packfile contains the corrupted object.

Note that we don't yet need the information about the specific packfile,
so we could've just as well made this a `bool *corrupted` pointer. But
we'll need information about the containing packfile in a subsequent
commit so that we can generate a proper error message telling the user
which packfile contains the broken object.

Signed-off-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2026-08-19 10:23:02 -07:00
2026-07-19 10:42:15 -07:00
2026-08-18 09:31:36 -07:00
2026-08-18 09:31:36 -07:00
2026-08-18 09:31:36 -07:00
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
2026-06-08 00:21:35 +09:00
2026-07-30 10:32:04 -07:00
2026-06-15 07:41:59 -07:00
…
…
2026-07-16 14:10:08 -07:00
2026-07-16 14:10:08 -07:00
…
…
2026-06-05 22:27:24 +09:00
…
2026-05-30 07:07:27 +09:00
…
2026-05-30 07:07:27 +09:00
2026-07-30 10:32:03 -07:00
…
…
…
…
…
…
…
2026-07-06 15:50:25 -07:00
2026-06-18 09:46:56 -07:00
2026-07-07 10:49:40 -07:00
…
…
…
…
…
…
…
…
…
…
…
2026-06-15 07:42:00 -07:00
2026-07-16 23:05:47 -07:00
…
…
…
…
…
…
…
2026-07-15 13:24:19 -07:00
…
…
…
…
2026-08-18 09:31:36 -07:00
2026-07-31 08:52:16 -07:00
2026-07-31 08:52:16 -07:00
…
…
2026-08-18 09:31:36 -07:00
…
…
…
…
…
…
…
…
…
2026-07-07 17:48:57 -07:00
…
…
2026-07-06 15:50:23 -07:00
2026-06-09 10:04:50 +09:00
…
…
…
…
2026-08-15 09:20:27 -07:00
…
…
…
2026-07-06 15:50:25 -07:00
…
2026-07-15 13:24:19 -07:00
2026-08-15 09:20:27 -07:00
…
…
2026-07-24 08:46:59 -07:00
…
2026-07-07 10:49:40 -07:00
…
2026-08-18 09:31:36 -07:00
…
…
…
…
…
…
…
2026-07-14 12:54:25 -07:00
2026-07-14 12:54:25 -07:00
…
…
2026-07-07 10:49:40 -07:00
…
…
…
2026-05-30 07:07:27 +09:00
…
…
…
2026-07-07 17:48:57 -07:00
2026-07-23 07:14:34 -07:00
…
…
…
…
…
…
…
…
…

GitHub build status GitLab build status

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.adoc to get started, then see Documentation/giteveryday.adoc for a useful minimum set of commands, and Documentation/git-<commandname>.adoc 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.adoc (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 and Documentation/CodingGuidelines).

Those wishing to help with error message, usage and informational message string translations (localization l10) should see po/README.md (a po file is a Portable Object file that holds the translations).

To subscribe to the list, send an email to git+subscribe@vger.kernel.org (see https://subspace.kernel.org/subscribing.html for details). The mailing list archives are available at https://lore.kernel.org/git/, https://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
Languages
C 49.8%
Shell 39.8%
Perl 4.3%
Tcl 3%
Python 0.8%
Other 2.1%