Taylor Blau d31d1f2e06 pack-objects: refactor read_packs_list_from_stdin() to use strmap
The '--stdin-packs' mode of pack-objects maintains two separate
string_lists: one for included packs, and one for excluded packs. Each
list stores the pack basename as a string and the corresponding
`packed_git` pointer in its `->util` field.

This works, but makes it awkward to extend the set of pack "kinds" that
pack-objects can accept via stdin, since each new kind would need its
own string_list and duplicated handling. A future commit will want to do
just this, so prepare for that change by handling the various "kinds" of
packs specified over stdin in a more generic fashion.

Namely, replace the two `string_list`s with a single `strmap` keyed on
the pack basename, with values pointing to a new `struct
stdin_pack_info`. This struct tracks both the `packed_git` pointer and a
`kind` bitfield indicating whether the pack was specified as included or
excluded.

Extract the logic for sorting packs by mtime and adding their objects
into a separate `stdin_packs_add_pack_entries()` helper.

While we could have used a `string_list`, we must handle the case where
the same pack is specified more than once. With a `string_list` only, we
would have to pay a quadratic cost to either (a) insert elements into
their sorted positions, or (b) a repeated linear search, which is
accidentally quadratic. For that reason, use a strmap instead.

This patch does not include any functional changes.

Signed-off-by: Taylor Blau <me@ttaylorr.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2026-03-27 13:40:39 -07:00
2026-03-19 09:54:57 -07:00
2026-02-03 09:41:52 -08:00
2026-03-09 14:36:55 -07:00
2026-01-13 05:41:17 -08:00
2025-12-07 07:28:13 +09:00
2026-01-09 18:36:16 -08:00
2026-02-07 17:41:03 -08:00
2026-02-09 12:09:09 -08:00
2026-02-23 13:23:41 -08:00
2026-02-23 13:23:41 -08:00
2026-03-09 14:36:55 -07:00
2026-02-05 15:42:01 -08:00
2026-03-10 14:23:24 -07:00
2026-03-10 14:23:24 -07:00
2026-02-19 13:23:41 -08:00
2026-02-17 13:30:41 -08:00
2026-03-16 10:48:15 -07:00
2026-03-16 10:48:15 -07:00
2026-02-23 13:21:19 -08:00
2026-03-16 10:48:15 -07:00
2025-11-25 12:15:59 -08:00
2025-11-25 12:15:59 -08:00
2026-02-23 13:21:18 -08:00
2026-03-16 10:48:15 -07:00
2026-03-12 14:09:07 -07:00
2026-03-12 14:09:07 -07:00
2026-02-20 08:13:58 -08:00
2026-02-08 15:03:06 -08:00
2026-03-09 14:36:55 -07:00
2026-03-10 14:23:18 -07:00
2026-03-09 14:36:55 -07:00
2026-02-05 15:42:01 -08:00
2026-03-09 14:36:55 -07:00
2026-01-22 10:58:14 -08:00
2026-03-19 09:54:56 -07:00
2026-03-06 13:02:20 -08:00
2025-12-29 22:02:54 +09:00
2026-03-10 14:23:18 -07:00
2026-01-09 18:36:17 -08:00
2026-01-09 18:36:17 -08:00
2026-03-09 14:36:55 -07:00
2026-02-08 15:16:49 -08:00
2026-02-08 15:16:49 -08:00
2025-12-07 07:28:11 +09:00
2025-11-12 14:04:04 -08: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 616 MiB
Languages
C 49.9%
Shell 39.5%
Perl 4.3%
Tcl 3%
Python 0.8%
Other 2.2%