Taylor Blau c7a120722e repack: introduce new compilation unit
Over the years, builtin/repack.c has turned into a grab-bag of
functionality powering the 'git repack' builtin. Among its many
capabilities, it:

 - can build and spawn 'git pack-objects' commands, which in turn
   generate new packs
 - has infrastructure to manage the set of existing packs in a
   repository
 - has infrastructure to split a sequence of packs into a geometric
   progression based on object size
 - can manage both generating and combining cruft packs together
 - can write new MIDXs

to name a few.

As a result, this builtin has accumulated a lot of code, making adding
new functionality difficult. In the future, 'repack' will learn how to
manage a chain of incremental MIDXs, adding yet more functionality into
the builtin.

As a prerequisite step, let's first move some of the functionality in
the builtin into its own repack.[ch].

This will be done over the course of many steps, since there are many
individual components, some of which will end up in other, yet-to-exist
compilation units of their own. Some of the code movement here is also
non-trivial, so performing it in individual steps will make it easier to
verify.

Let's start by migrating 'struct pack_objects_args' (and the related
corresponding pack_objects_args_release() function) into repack.h, and
teach both the Makefile and Meson how to build the new compilation unit.

Signed-off-by: Taylor Blau <me@ttaylorr.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-10-16 10:08:53 -07:00
2025-08-04 08:10:34 -07:00
2025-09-23 11:53:40 -07:00
2025-09-06 11:59:48 +02:00
2023-11-26 10:07:06 +09:00
2025-08-02 22:44:58 -07:00
2025-07-01 07:46:22 -07:00
2025-09-08 14:54:35 -07:00
2025-07-01 14:46:38 -07:00
2025-07-01 14:46:38 -07:00
2025-09-08 14:54:35 -07:00
2025-07-15 15:18:18 -07:00
2024-09-16 10:46:00 -07:00
2024-06-14 10:26:33 -07:00
2024-06-14 10:26:33 -07:00
2024-01-23 10:40:10 -08:00
2025-09-08 14:54:35 -07:00
2025-08-21 13:46:58 -07:00
2025-08-04 08:10:33 -07:00
2025-08-21 13:46:59 -07:00
2025-07-23 08:15:18 -07:00
2024-06-14 10:26:33 -07:00
2025-01-21 08:44:54 -08:00
2025-01-21 08:44:54 -08:00
2024-04-05 15:21:14 -07:00
2024-12-18 10:44:31 -08:00
2025-08-25 14:22:01 -07:00
2025-08-25 14:22:01 -07:00
2025-03-03 13:49:23 -08:00
2025-08-25 14:22:01 -07:00
2025-07-01 14:46:38 -07:00
2025-07-23 08:15:18 -07:00
2024-10-23 16:16:36 -04:00
2024-10-23 16:16:36 -04:00
2024-10-23 16:16:36 -04:00
2024-09-19 13:46:00 -07:00
2025-09-08 14:54:35 -07:00
2024-12-18 10:44:31 -08:00
2023-11-26 10:07:05 +09:00
2025-07-01 14:46:38 -07:00
2025-05-08 12:36:31 -07:00
2025-07-15 15:18:18 -07:00
2025-07-01 14:46:38 -07:00
2025-08-21 13:46:57 -07:00
2024-10-23 16:16:36 -04:00
2023-11-26 10:07:05 +09:00
2025-07-01 14:46:38 -07:00
2023-11-26 10:07:05 +09:00
2025-07-23 08:15:18 -07:00
2024-12-18 10:44:31 -08:00
2025-07-01 14:46:38 -07:00
2025-07-23 08:15:18 -07:00
2025-08-21 13:47:02 -07:00
2024-02-26 15:34:01 -08:00
2025-08-21 13:46:59 -07:00
2025-04-23 13:58:50 -07:00
2025-05-12 13:06:26 -07:00
2024-10-21 16:05:04 -04:00
2024-06-14 10:26:33 -07:00
2025-07-15 15:18:18 -07:00
2024-12-18 10:44:30 -08:00
2024-12-18 10:44:30 -08:00
2025-08-25 14:22:00 -07:00
2025-07-01 14:58:24 -07:00
2025-07-23 08:15:18 -07:00
2024-12-18 10:44:30 -08:00
2025-07-01 14:46:37 -07:00
2025-08-21 13:46:59 -07:00
2023-11-26 10:07:05 +09:00
2024-09-19 13:46:01 -07:00
2024-04-05 15:21:14 -07:00
2025-08-21 13:46:58 -07:00
2025-08-21 13:46:58 -07:00
2025-08-21 13:46:58 -07:00
2025-08-21 13:46:58 -07:00
2025-08-21 13:47:03 -07:00
2025-06-17 10:44:38 -07:00
2025-06-17 10:44:38 -07:00
2024-06-14 10:26:33 -07:00
2024-09-19 13:46:12 -07:00
2025-07-15 15:18:18 -07:00
2025-07-01 14:58:24 -07:00
2024-12-18 10:44:30 -08:00
2025-08-21 13:46:59 -07:00
2023-11-26 10:07:05 +09:00
2025-07-01 14:46:38 -07:00
2024-12-27 08:12:40 -08:00
2024-09-30 11:23:03 -07:00
2024-06-14 10:26:33 -07:00
2023-09-15 17:08:46 -07:00
2025-07-01 14:46:37 -07:00
2024-12-23 09:32:11 -08:00
2025-07-01 14:46:38 -07:00
2024-05-17 10:33:39 -07:00
2025-03-03 13:49:26 -08:00
2024-12-18 10:44:30 -08:00
2024-12-18 10:44:30 -08:00
2025-07-23 08:15:18 -07:00
2025-03-03 13:49:27 -08:00
2025-07-01 14:46:38 -07:00
2025-02-06 14:56:45 -08:00
2025-05-15 17:24:55 -07:00
2025-08-21 13:47:00 -07:00

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
Description
No description provided
Readme 581 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%