To: git@vger.kernel.org
-Subject: What's cooking in git.git (May 2024, #08; Mon, 20)
-X-master-at: 4365c6fcf96caac73dcc412aa25db34cf8df48d5
-X-next-at: 888b28324335471fe2b21105063128ca8fa54801
+Subject: What's cooking in git.git (May 2024, #09; Thu, 23)
+X-master-at: b9cfe4845cb2562584837bc0101c0ab76490a239
+X-next-at: bbe1065a7e6f9ab964c30003b9eadf3a65c611d5
Bcc: lwn@lwn.net, gitster@pobox.com
-What's cooking in git.git (May 2024, #08; Mon, 20)
+What's cooking in git.git (May 2024, #09; Thu, 23)
--------------------------------------------------
Here are the topics that have been cooking in my tree. Commits
no activity (of course they can be resubmit when new interests
arise).
+We unfortunately had serious regressions in 2.45.1 (and below, down
+to 2.39 maintenance track are affected), and we are trying to assess
+the extent of damage and which changes that went into the release to
+revert. We know about "git lfs" and "git annex" getting affected.
+If your workflow is affected, you would want to try out 'seen' that
+has proposed reverts to alleviate and report back to us, to make sure
+that the next set of maintenance releases will fix the regressions
+for you.
+
Copies of the source code to Git live in many repositories, and the
following is a list of the ones I push into or their mirrors. Some
repositories have only a subset of branches.
https://www.kernel.org/pub/software/scm/git/
--------------------------------------------------
-[New Topics]
+[Graduated to 'master']
-* es/chainlint-ncores-fix (2024-05-20) 3 commits
- - chainlint.pl: latch CPU count directly reported by /proc/cpuinfo
- - chainlint.pl: fix incorrect CPU count on Linux SPARC
- - chainlint.pl: make CPU count computation more robust
+* dg/fetch-pack-code-cleanup (2024-05-13) 1 commit
+ (merged to 'next' on 2024-05-17 at c8f8136d2e)
+ + fetch-pack: remove unused 'struct loose_object_iter'
- The chainlint script (invoked during "make test") did nothing when
- it failed to detect the number of available CPUs. It now falls
- back to 1 CPU to avoid the problem.
+ Code clean-up to remove an unused struct definition.
+ source: <20240512005913.342287-1-dave@treblig.org>
+
+
+* dm/update-index-doc-fix (2024-05-13) 1 commit
+ (merged to 'next' on 2024-05-17 at 2f6cd0d1cc)
+ + documentation: git-update-index: add --show-index-version to synopsis
+
+ Doc fix.
+ source: <20240512031400.28416-1-dov.murik@linux.dev>
+
+
+* it/refs-name-conflict (2024-05-06) 1 commit
+ (merged to 'next' on 2024-05-15 at 39ef3ecc88)
+ + refs: return conflict error when checking packed refs
+
+ Expose "name conflict" error when a ref creation fails due to D/F
+ conflict in the ref namespace, to improve an error message given by
+ "git fetch".
+ source: <pull.1716.v3.git.git.1714791848557.gitgitgadget@gmail.com>
- Will merge to 'next'.
- source: <20240520190131.94904-1-ericsunshine@charter.net>
+
+* jc/patch-flow-updates (2024-05-10) 2 commits
+ (merged to 'next' on 2024-05-16 at d7a885574b)
+ + SubmittingPatches: extend the "flow" section
+ + SubmittingPatches: move the patch-flow section earlier
+ (this branch is used by kn/patch-iteration-doc.)
+
+ Doc updates.
+ source: <20240510165526.1412338-1-gitster@pobox.com>
+
+
+* la/hide-trailer-info (2024-05-02) 11 commits
+ (merged to 'next' on 2024-05-15 at 955ffe4f37)
+ + trailer unit tests: inspect iterator contents
+ + trailer: document parse_trailers() usage
+ + trailer: retire trailer_info_get() from API
+ + trailer: make trailer_info struct private
+ + trailer: make parse_trailers() return trailer_info pointer
+ + interpret-trailers: access trailer_info with new helpers
+ + sequencer: use the trailer iterator
+ + trailer: teach iterator about non-trailer lines
+ + trailer: add unit tests for trailer iterator
+ + Makefile: sort UNIT_TEST_PROGRAMS
+ + Merge branch 'la/format-trailer-info' into la/hide-trailer-info
+
+ The trailer API has been reshuffled a bit.
+ source: <pull.1696.v4.git.1714625667.gitgitgadget@gmail.com>
+
+
+* mt/openindiana-portability (2024-05-17) 7 commits
+ (merged to 'next' on 2024-05-17 at de53f37879)
+ + t/t9001-send-email.sh: sed - remove the i flag for s
+ + t/t9118-git-svn-funky-branch-names.sh: sed needs semicolon
+ + t/t1700-split-index.sh: mv -v is not portable
+ + t/t4202-log.sh: fix misspelled variable
+ + t/t0600-reffiles-backend.sh: rm -v is not portable
+ + t/t9902-completion.sh: backslashes in echo
+ + Switch grep from non-portable BRE to portable ERE
+
+ Portability updates to various uses of grep and sed.
+ source: <ZkeMiifGHkIsehz3@telcontar>
--------------------------------------------------
-[Graduated to 'master']
+[New Topics]
-* jc/compat-regex-calloc-fix (2024-05-13) 1 commit
- (merged to 'next' on 2024-05-13 at 077c4e1dcc)
- + compat/regex: fix argument order to calloc(3)
+* gt/unit-test-strcmp-offset (2024-05-20) 1 commit
+ (merged to 'next' on 2024-05-23 at f672ec425f)
+ + t/: port helper/test-strcmp-offset.c to unit-tests/t-strcmp-offset.c
- Windows CI running in GitHub Actions started complaining about the
- order of arguments given to calloc(); the imported regex code uses
- the wrong order almost consistently, which has been corrected.
- source: <xmqqbk5bim2n.fsf@gitster.g>
+ The strcmp-offset tests have been rewritten using the unit test
+ framework.
+ Will merge to 'master'.
+ source: <20240519204530.12258-3-shyamthakkar001@gmail.com>
-* kn/ref-transaction-symref (2024-05-07) 8 commits
- (merged to 'next' on 2024-05-11 at 0a7119f2a3)
- + refs: remove `create_symref` and associated dead code
- + refs: rename `refs_create_symref()` to `refs_update_symref()`
- + refs: use transaction in `refs_create_symref()`
- + refs: add support for transactional symref updates
- + refs: move `original_update_refname` to 'refs.c'
- + refs: support symrefs in 'reference-transaction' hook
- + files-backend: extract out `create_symref_lock()`
- + refs: accept symref values in `ref_transaction_update()`
- (this branch is used by kn/update-ref-symref.)
- Updates to symbolic refs can now be made as a part of ref
- transaction.
- source: <20240507125859.132116-1-knayak@gitlab.com>
+* jc/add-patch-enforce-single-letter-input (2024-05-22) 1 commit
+ (merged to 'next' on 2024-05-23 at 12fef48392)
+ + add-patch: enforce only one-letter response to prompts
+
+ "git add -p" learned to complain when an answer with more than one
+ letter is given to a prompt that expects a single letter answer.
+
+ Will merge to 'master'.
+ source: <xmqqh6ep1pwz.fsf_-_@gitster.g>
+
+
+* jc/fix-2.45.1-and-friends-for-2.39 (2024-05-22) 12 commits
+ - Revert "fsck: warn about symlink pointing inside a gitdir"
+ - Revert "Add a helper function to compare file contents"
+ - clone: drop the protections where hooks aren't run
+ - tests: verify that `clone -c core.hooksPath=/dev/null` works again
+ - Revert "core.hooksPath: add some protection while cloning"
+ - init: use the correct path of the templates directory again
+ - hook: plug a new memory leak
+ - ci: stop installing "gcc-13" for osx-gcc
+ - ci: avoid bare "gcc" for osx-gcc job
+ - ci: drop mention of BREW_INSTALL_PACKAGES variable
+ - send-email: avoid creating more than one Term::ReadLine object
+ - send-email: drop FakeTerm hack
+ (this branch is used by jc/fix-2.45.1-and-friends-for-maint.)
+
+ Revert overly aggressive "layered defence" that went into 2.45.1
+ and friends, which broke "git-lfs", "git-annex", and other use
+ cases, so that we can rebuild necessary counterparts in the open.
+
+ Needs consensus on what (more) to revert or adjust.
+ source: <20240521195659.870714-1-gitster@pobox.com>
+
+
+* jc/fix-2.45.1-and-friends-for-maint (2024-05-22) 12 commits
+ - Merge branch 'fixes/2.45.1/2.44' into jc/fix-2.45.1-and-friends-for-maint
+ - Merge branch 'fixes/2.45.1/2.43' into fixes/2.45.1/2.44
+ - Merge branch 'fixes/2.45.1/2.42' into fixes/2.45.1/2.43
+ - Merge branch 'fixes/2.45.1/2.41' into fixes/2.45.1/2.42
+ - Merge branch 'fixes/2.45.1/2.40' into fixes/2.45.1/2.41
+ - Merge branch 'jc/fix-2.45.1-and-friends-for-2.39' into fixes/2.45.1/2.40
+ - Merge branch 'fixes/2.45.1/2.44' into jc/fix-2.45.1-and-friends-for-maint
+ - Merge branch 'fixes/2.45.1/2.43' into fixes/2.45.1/2.44
+ - Merge branch 'fixes/2.45.1/2.42' into fixes/2.45.1/2.43
+ - Merge branch 'fixes/2.45.1/2.41' into fixes/2.45.1/2.42
+ - Merge branch 'fixes/2.45.1/2.40' into fixes/2.45.1/2.41
+ - Merge branch 'jc/fix-2.45.1-and-friends-for-2.39' into fixes/2.45.1/2.40
+ (this branch uses jc/fix-2.45.1-and-friends-for-2.39.)
+
+ Adjust jc/fix-2.45.1-and-friends-for-2.39 for more recent
+ maintenance track.
+
+ Will be merged to 'next' when the base topic becomes ready.
+
+
+* ps/fix-reinit-includeif-onbranch (2024-05-22) 1 commit
+ - setup: fix bug with "includeIf.onbranch" when initializing dir
+
+ "git init" in an already created directory, when the user
+ configuration has includeif.onbranch, started to fail recently,
+ which has been corrected.
+
+ Will merge to 'next'.
+ source: <cf182bb9ee7d4a7eb46e5dbf4f3ef5deb198d823.1716374321.git.ps@pks.im>
--------------------------------------------------
[Cooking]
+* es/chainlint-ncores-fix (2024-05-22) 3 commits
+ (merged to 'next' on 2024-05-22 at 1e4ab85522)
+ + chainlint.pl: latch CPU count directly reported by /proc/cpuinfo
+ + chainlint.pl: fix incorrect CPU count on Linux SPARC
+ + chainlint.pl: make CPU count computation more robust
+
+ The chainlint script (invoked during "make test") did nothing when
+ it failed to detect the number of available CPUs. It now falls
+ back to 1 CPU to avoid the problem.
+
+ Will merge to 'master'.
+ source: <20240520190131.94904-1-ericsunshine@charter.net>
+
+
* tb/pack-bitmap-write-cleanups (2024-05-15) 6 commits
(merged to 'next' on 2024-05-20 at 585e7bde21)
+ pack-bitmap: introduce `bitmap_writer_free()`
* kn/osxkeychain-skip-idempotent-store (2024-05-15) 2 commits
- - osxkeychain: state to skip unnecessary store operations
- - osxkeychain: exclusive lock to serialize execution of operations
+ (merged to 'next' on 2024-05-21 at 4d757167ad)
+ + osxkeychain: state to skip unnecessary store operations
+ + osxkeychain: exclusive lock to serialize execution of operations
The credential helper that talks with osx keychain learned to avoid
storing back the authentication material it just got received from
the keychain.
- Comments?
+ Will merge to 'master'.
source: <pull.1729.v3.git.1715800868.gitgitgadget@gmail.com>
-* kn/update-ref-symref (2024-05-15) 7 commits
+* kn/update-ref-symref (2024-05-23) 7 commits
- update-ref: add support for 'symref-update' command
- reftable: pick either 'oid' or 'target' for new updates
- update-ref: add support for 'symref-create' command
"git update-ref --stdin" learned to handle transactional updates of
symbolic-refs.
- Expecting a reroll.
- cf. <ZkXpcvF6dxGr6qmj@tanuki>
+ Needs review.
source: <20240514124411.1037019-1-knayak@gitlab.com>
* ps/refs-without-the-repository-updates (2024-05-17) 17 commits
- - refs/packed: remove references to `the_hash_algo`
- - refs/files: remove references to `the_hash_algo`
- - refs/files: use correct repository
- - refs: remove `dwim_log()`
- - refs: drop `git_default_branch_name()`
- - refs: pass repo when peeling objects
- - refs: move object peeling into "object.c"
- - refs: pass ref store when detecting dangling symrefs
- - refs: convert iteration over replace refs to accept ref store
- - refs: retrieve worktree ref stores via associated repository
- - refs: refactor `resolve_gitlink_ref()` to accept a repository
- - refs: pass repo when retrieving submodule ref store
- - refs: track ref stores via strmap
- - refs: implement releasing ref storages
- - refs: rename `init_db` callback to avoid confusion
- - refs: adjust names for `init` and `init_db` callbacks
- - Merge branch 'ps/refs-without-the-repository' into ps/refs-without-the-repository-updates
+ (merged to 'next' on 2024-05-22 at 744f37ab2b)
+ + refs/packed: remove references to `the_hash_algo`
+ + refs/files: remove references to `the_hash_algo`
+ + refs/files: use correct repository
+ + refs: remove `dwim_log()`
+ + refs: drop `git_default_branch_name()`
+ + refs: pass repo when peeling objects
+ + refs: move object peeling into "object.c"
+ + refs: pass ref store when detecting dangling symrefs
+ + refs: convert iteration over replace refs to accept ref store
+ + refs: retrieve worktree ref stores via associated repository
+ + refs: refactor `resolve_gitlink_ref()` to accept a repository
+ + refs: pass repo when retrieving submodule ref store
+ + refs: track ref stores via strmap
+ + refs: implement releasing ref storages
+ + refs: rename `init_db` callback to avoid confusion
+ + refs: adjust names for `init` and `init_db` callbacks
+ + Merge branch 'ps/refs-without-the-repository' into ps/refs-without-the-repository-updates
+ (this branch is used by ps/ref-storage-migration.)
Further clean-up the refs subsystem to stop relying on
the_repository, and instead use the repository associated to the
ref_store object.
- Will merge to 'next'?
+ Will merge to 'master'.
source: <cover.1715929858.git.ps@pks.im>
(merged to 'next' on 2024-05-20 at e0ee0051a9)
+ SubmittingPatches: add section for iterating patches
+ Merge branch 'jc/patch-flow-updates' into kn/patch-iteration-doc
- (this branch uses jc/patch-flow-updates.)
Doc updates.
source: <20240517122724.270706-1-knayak@gitlab.com>
-* mt/openindiana-portability (2024-05-17) 7 commits
- (merged to 'next' on 2024-05-17 at de53f37879)
- + t/t9001-send-email.sh: sed - remove the i flag for s
- + t/t9118-git-svn-funky-branch-names.sh: sed needs semicolon
- + t/t1700-split-index.sh: mv -v is not portable
- + t/t4202-log.sh: fix misspelled variable
- + t/t0600-reffiles-backend.sh: rm -v is not portable
- + t/t9902-completion.sh: backslashes in echo
- + Switch grep from non-portable BRE to portable ERE
-
- Portability updates to various uses of grep and sed.
-
- Will merge to 'master'.
- source: <ZkeMiifGHkIsehz3@telcontar>
-
-
* mt/openindiana-scalar (2024-05-17) 1 commit
- scalar: make enlistment delete to work on all POSIX platforms
* ts/archive-prefix-with-add-virtual-file (2024-05-17) 1 commit
- archive: make --add-virtual-file honor --prefix
+ The "--add-virtual-file" option of "git archive", added primarily
+ to help "git diagnose", has always ignored the "--prefix", but
+ been documented to honor it.
+
+ Iffy if updating the implementation is the best approach.
+ cf. <bc3711a7-37d5-46bc-979e-83bd0b2cf900@web.de>
source: <pull.1719.v2.git.git.1715967267420.gitgitgadget@gmail.com>
* js/doc-decisions (2024-05-17) 1 commit
- - doc: describe the project's decision-making process
+ (merged to 'next' on 2024-05-22 at 891a062720)
+ + doc: describe the project's decision-making process
The project decision making policy has been documented.
+
+ Will merge to 'master'.
source: <10f217915600eda3ebec886e4f020f87c22e318a.1715978031.git.steadmon@google.com>
-* jc/undecided-is-not-necessarily-sha1-fix (2024-05-16) 6 commits
- - apply: fix uninitialized hash function
- - builtin/hash-object: fix uninitialized hash function
- - builtin/patch-id: fix uninitialized hash function
- - t1517: test commands that are designed to be run outside repository
- - setup: add an escape hatch for "no more default hash algorithm" change
- - Merge branch 'ps/undecided-is-not-necessarily-sha1' into jc/undecided-is-not-necessarily-sha1-fix
+* jc/undecided-is-not-necessarily-sha1-fix (2024-05-21) 6 commits
+ (merged to 'next' on 2024-05-22 at 4bd7982ebe)
+ + apply: fix uninitialized hash function
+ + builtin/hash-object: fix uninitialized hash function
+ + builtin/patch-id: fix uninitialized hash function
+ + t1517: test commands that are designed to be run outside repository
+ + setup: add an escape hatch for "no more default hash algorithm" change
+ + Merge branch 'ps/undecided-is-not-necessarily-sha1' into jc/undecided-is-not-necessarily-sha1-fix
(this branch uses ps/undecided-is-not-necessarily-sha1.)
The base topic started to make it an error for a command to leave
the "default is sha-1" behaviour as an escape hatch, and start
fixing these breakages.
- Broken.
- The hash-object test does not seem to work with SHA-256 repositories.
- source: <20240513224127.2042052-1-gitster@pobox.com>
-
-
-* dg/fetch-pack-code-cleanup (2024-05-13) 1 commit
- (merged to 'next' on 2024-05-17 at c8f8136d2e)
- + fetch-pack: remove unused 'struct loose_object_iter'
-
- Code clean-up to remove an unused struct definition.
-
- Will merge to 'master'.
- source: <20240512005913.342287-1-dave@treblig.org>
-
-
-* dm/update-index-doc-fix (2024-05-13) 1 commit
- (merged to 'next' on 2024-05-17 at 2f6cd0d1cc)
- + documentation: git-update-index: add --show-index-version to synopsis
-
- Doc fix.
-
Will merge to 'master'.
- source: <20240512031400.28416-1-dov.murik@linux.dev>
+ source: <20240520231434.1816979-1-gitster@pobox.com>
* ps/builtin-config-cleanup (2024-05-15) 22 commits
* ps/reftable-reusable-iterator (2024-05-13) 13 commits
- - reftable/merged: adapt interface to allow reuse of iterators
- - reftable/stack: provide convenience functions to create iterators
- - reftable/reader: adapt interface to allow reuse of iterators
- - reftable/generic: adapt interface to allow reuse of iterators
- - reftable/generic: move seeking of records into the iterator
- - reftable/merged: simplify indices for subiterators
- - reftable/merged: split up initialization and seeking of records
- - reftable/reader: set up the reader when initializing table iterator
- - reftable/reader: inline `reader_seek_internal()`
- - reftable/reader: separate concerns of table iter and reftable reader
- - reftable/reader: unify indexed and linear seeking
- - reftable/reader: avoid copying index iterator
- - reftable/block: use `size_t` to track restart point index
+ (merged to 'next' on 2024-05-22 at b92eb9939f)
+ + reftable/merged: adapt interface to allow reuse of iterators
+ + reftable/stack: provide convenience functions to create iterators
+ + reftable/reader: adapt interface to allow reuse of iterators
+ + reftable/generic: adapt interface to allow reuse of iterators
+ + reftable/generic: move seeking of records into the iterator
+ + reftable/merged: simplify indices for subiterators
+ + reftable/merged: split up initialization and seeking of records
+ + reftable/reader: set up the reader when initializing table iterator
+ + reftable/reader: inline `reader_seek_internal()`
+ + reftable/reader: separate concerns of table iter and reftable reader
+ + reftable/reader: unify indexed and linear seeking
+ + reftable/reader: avoid copying index iterator
+ + reftable/block: use `size_t` to track restart point index
Code clean-up to make the reftable iterator closer to be reusable.
- Comments?
+ Will merge to 'master'.
source: <cover.1715589670.git.ps@pks.im>
-* tb/precompose-getcwd (2024-05-09) 1 commit
- (merged to 'next' on 2024-05-11 at d1b507b01a)
- + macOS: ls-files path fails if path of workdir is NFD
+* tb/precompose-getcwd (2024-05-21) 1 commit
+ - macOS: ls-files path fails if path of workdir is NFD
We forgot to normalize the result of getcwd() to NFC on macOS where
all other paths are normalized, which has been corrected.
- On hold.
+ Reverted out of 'next' to be replaced with an updated version (this one).
+ Expectign a reroll to clarify the proposed log message.
cf. <20240520160601.GA29154@tb-raspi4>
- source: <20240509161110.12121-1-tboegi@web.de>
-
-
-* jc/patch-flow-updates (2024-05-10) 2 commits
- (merged to 'next' on 2024-05-16 at d7a885574b)
- + SubmittingPatches: extend the "flow" section
- + SubmittingPatches: move the patch-flow section earlier
- (this branch is used by kn/patch-iteration-doc.)
-
- Doc updates.
-
- Will merge to 'master'.
- source: <20240510165526.1412338-1-gitster@pobox.com>
-
-
-* it/refs-name-conflict (2024-05-06) 1 commit
- (merged to 'next' on 2024-05-15 at 39ef3ecc88)
- + refs: return conflict error when checking packed refs
-
- Expose "name conflict" error when a ref creation fails due to D/F
- conflict in the ref namespace, to improve an error message given by
- "git fetch".
-
- Will merge to 'master'.
- source: <pull.1716.v3.git.git.1714791848557.gitgitgadget@gmail.com>
+ cf. <20240521205749.GA8165@tb-raspi4>
+ source: <20240521141452.26210-1-tboegi@web.de>
* jc/format-patch-more-aggressive-range-diff (2024-05-06) 1 commit
- - format-patch: run range-diff with larger creation-factor
+ (merged to 'next' on 2024-05-21 at 899cce93fb)
+ + format-patch: run range-diff with larger creation-factor
The default "creation-factor" used by "git format-patch" has been
raised to make it more aggressively find matching commits.
- Comments?
+ Will merge to 'master'.
source: <xmqqbk5i3ncw.fsf_-_@gitster.g>
* ps/reftable-write-options (2024-05-13) 11 commits
- - refs/reftable: allow configuring geometric factor
- - reftable: make the compaction factor configurable
- - refs/reftable: allow disabling writing the object index
- - refs/reftable: allow configuring restart interval
- - reftable: use `uint16_t` to track restart interval
- - refs/reftable: allow configuring block size
- - reftable/dump: support dumping a table's block structure
- - reftable/writer: improve error when passed an invalid block size
- - reftable/writer: drop static variable used to initialize strbuf
- - reftable: pass opts as constant pointer
- - reftable: consistently refer to `reftable_write_options` as `opts`
+ (merged to 'next' on 2024-05-22 at ae8e378430)
+ + refs/reftable: allow configuring geometric factor
+ + reftable: make the compaction factor configurable
+ + refs/reftable: allow disabling writing the object index
+ + refs/reftable: allow configuring restart interval
+ + reftable: use `uint16_t` to track restart interval
+ + refs/reftable: allow configuring block size
+ + reftable/dump: support dumping a table's block structure
+ + reftable/writer: improve error when passed an invalid block size
+ + reftable/writer: drop static variable used to initialize strbuf
+ + reftable: pass opts as constant pointer
+ + reftable: consistently refer to `reftable_write_options` as `opts`
The knobs to tweak how reftable files are written have been made
available as configuration variables.
- Comments?
+ Will merge to 'master'.
source: <cover.1715587849.git.ps@pks.im>
+ Documentation/glossary: define root refs as refs
+ Documentation/glossary: clarify limitations of pseudorefs
+ Documentation/glossary: redefine pseudorefs as special refs
+ (this branch is used by ps/ref-storage-migration.)
Terminology to call various ref-like things are getting
straightened out.
* jc/rev-parse-fatal-doc (2024-05-01) 1 commit
- - rev-parse: document how --is-* options work outside a repository
+ (merged to 'next' on 2024-05-21 at 9bbb973b7b)
+ + rev-parse: document how --is-* options work outside a repository
Doc update.
- Comments?
+ Will merge to 'master'.
source: <xmqqplu54fbg.fsf@gitster.g>
source: <20240328101356.300374-1-e@80x24.org>
-* la/hide-trailer-info (2024-05-02) 11 commits
- (merged to 'next' on 2024-05-15 at 955ffe4f37)
- + trailer unit tests: inspect iterator contents
- + trailer: document parse_trailers() usage
- + trailer: retire trailer_info_get() from API
- + trailer: make trailer_info struct private
- + trailer: make parse_trailers() return trailer_info pointer
- + interpret-trailers: access trailer_info with new helpers
- + sequencer: use the trailer iterator
- + trailer: teach iterator about non-trailer lines
- + trailer: add unit tests for trailer iterator
- + Makefile: sort UNIT_TEST_PROGRAMS
- + Merge branch 'la/format-trailer-info' into la/hide-trailer-info
-
- The trailer API has been reshuffled a bit.
-
- Will merge to 'master'.
- source: <pull.1696.v4.git.1714625667.gitgitgadget@gmail.com>
-
-
* ds/doc-config-reflow (2024-03-14) 1 commit
- config.txt: perform some minor reformatting
Not ready to be reviewed yet.
source: <20230824205456.1231371-1-gitster@pobox.com>
-
---------------------------------------------------
-[Discarded]
-
-* tb/pseudo-merge-reachability-bitmap (2024-04-30) 23 commits
- . t/perf: implement performace tests for pseudo-merge bitmaps
- . pseudo-merge: implement support for finding existing merges
- . ewah: `bitmap_equals_ewah()`
- . pack-bitmap: extra trace2 information
- . pack-bitmap.c: use pseudo-merges during traversal
- . t/test-lib-functions.sh: support `--date` in `test_commit_bulk()`
- . pack-bitmap: implement test helpers for pseudo-merge
- . ewah: implement `ewah_bitmap_popcount()`
- . pseudo-merge: implement support for reading pseudo-merge commits
- . pack-bitmap.c: read pseudo-merge extension
- . pseudo-merge: scaffolding for reads
- . pack-bitmap: extract `read_bitmap()` function
- . pack-bitmap-write.c: write pseudo-merge table
- . pack-bitmap-write.c: select pseudo-merge commits
- . pseudo-merge: implement support for selecting pseudo-merge commits
- . pack-bitmap: make `bitmap_writer_push_bitmapped_commit()` public
- . pack-bitmap: implement `bitmap_writer_has_bitmapped_object_id()`
- . pack-bitmap-write: support storing pseudo-merge commits
- . pseudo-merge.ch: initial commit
- . pack-bitmap: move some initialization to `bitmap_writer_init()`
- . pack-bitmap: drop unused `max_bitmaps` parameter
- . ewah: implement `ewah_bitmap_is_subset()`
- . Documentation/technical: describe pseudo-merge bitmaps format
-
- The pack-bitmap machinery learned to write pseudo-merge bitmaps,
- which act as imaginary octopus merges covering un-bitmapped
- reference tips. This enhances bitmap coverage, and thus,
- performance, for repositories with many references using bitmaps.
-
- Retracted to be rebuilt on top of tb/pack-bitmap-write-cleanups topic
- source: <cover.1714422410.git.me@ttaylorr.com>
projects / thirdparty / git.git / commitdiff
