{"thread":{"id":"61962","subject":"What's cooking in git.git (Aug 2024, #06; Fri, 16)","startedAt":"2024-08-16T18:42:25Z","lastAt":"2024-08-20T20:41:41Z","messageCount":5,"participants":["Junio C Hamano","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"501160","messageId":"xmqqwmkgjomp.fsf@gitster.g","threadId":"61962","inReplyTo":null,"subject":"What's cooking in git.git (Aug 2024, #06; Fri, 16)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2024-08-16T18:42:22Z","receivedAt":"2024-08-16T18:42:25Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Here are the topics that have been cooking in my tree. Commits\nprefixed with '+' are in 'next' (being in 'next' is a sign that a\ntopic is stable enough to be used and are candidate to be in a\nfuture release). Commits prefixed with '-' are only in 'seen', and\naren't considered \"accepted\" at all and may be annotated with an URL\nto a message that raises issues but they are no means exhaustive. A\ntopic without enough support may be discarded after a long period of\nno activity (of course they can be resubmit when new interests\narise).\n\nCopies of the source code to Git live in many repositories, and the\nfollowing is a list of the ones I push into or their mirrors. Some\nrepositories have only a subset of branches.\n\nWith maint, master, next, seen, todo:\n\n\tgit://git.kernel.org/pub/scm/git/git.git/\n\tgit://repo.or.cz/alt-git.git/\n\thttps://kernel.googlesource.com/pub/scm/git/git/\n\thttps://github.com/git/git/\n\thttps://gitlab.com/git-scm/git/\n\nWith all the integration branches and topics broken out:\n\n\thttps://github.com/gitster/git/\n\nEven though the preformatted documentation in HTML and man format\nare not sources, they are published in these repositories for\nconvenience (replace \"htmldocs\" with \"manpages\" for the manual\npages):\n\n\tgit://git.kernel.org/pub/scm/git/git-htmldocs.git/\n\thttps://github.com/gitster/git-htmldocs.git/\n\nRelease tarballs are available at:\n\n\thttps://www.kernel.org/pub/software/scm/git/\n\n--------------------------------------------------\n[Graduated to 'master']\n\n* ag/t7004-modernize (2024-08-08) 8 commits\n (merged to 'next' on 2024-08-09 at 7bce577df4)\n + t7004: make use of write_script\n + t7004: use single quotes instead of double quotes\n + t7004: begin the test body on the same line as test_expect_success\n + t7004: description on the same line as test_expect_success\n + t7004: do not prepare things outside test_expect_success\n + t7004: use indented here-doc\n + t7004: one command per line\n + t7004: remove space after redirect operators\n\n Coding style fixes to a test script.\n source: <20240808163302.17521-1-abdobngad@gmail.com>\n\n\n* es/doc-platform-support-policy (2024-08-02) 1 commit\n (merged to 'next' on 2024-08-09 at 110c94ea82)\n + Documentation: add platform support policy\n\n A policy document that describes platform support levels and\n expectation on platform stakeholders has been introduced.\n source: <20240802221948.2367124-1-emilyshaffer@google.com>\n\n\n* gt/unit-test-hashmap (2024-08-06) 1 commit\n (merged to 'next' on 2024-08-09 at e62febfb4e)\n + t: port helper/test-hashmap.c to unit-tests/t-hashmap.c\n\n An existing test of hashmap API has been rewritten with the\n unit-test framework.\n cf. \n source: <20240803133517.73308-2-shyamthakkar001@gmail.com>\n\n\n* jc/refs-symref-referent (2024-08-09) 3 commits\n (merged to 'next' on 2024-08-09 at 3183f3d05b)\n + ref-filter: populate symref from iterator\n + refs: add referent to each_ref_fn\n + refs: keep track of unresolved reference value in iterators\n\n The refs API has been taught to give symref target information to\n the users of ref iterators, allowing for-each-ref and friends to\n avoid an extra ref_resolve_* API call per a symbolic ref.\n source: \n\n\n* jc/safe-directory (2024-07-30) 4 commits\n (merged to 'next' on 2024-08-05 at 77aa0f1d08)\n + safe.directory: setting safe.directory=\".\" allows the \"current\" directory\n + safe.directory: normalize the configured path\n + safe.directory: normalize the checked path\n + safe.directory: preliminary clean-up\n\n Follow-up on 2.45.1 regression fix.\n source: <20240730184352.2503276-1-gitster@pobox.com>\n\n\n* jc/t3206-test-when-finished-fix (2024-08-06) 1 commit\n (merged to 'next' on 2024-08-08 at 46461db3a2)\n + t3206: test_when_finished before dirtying operations, not after\n\n Test clean-up.\n source: \n\n\n* ps/reftable-stack-compaction (2024-08-08) 9 commits\n (merged to 'next' on 2024-08-09 at d7875bf14b)\n + reftable/stack: handle locked tables during auto-compaction\n + reftable/stack: fix corruption on concurrent compaction\n + reftable/stack: use lock_file when adding table to \"tables.list\"\n + reftable/stack: do not die when fsyncing lock file files\n + reftable/stack: simplify tracking of table locks\n + reftable/stack: update stats on failed full compaction\n + reftable/stack: test compaction with already-locked tables\n + reftable/stack: extract function to setup stack with N tables\n + reftable/stack: refactor function to gather table sizes\n (this branch is used by ps/reftable-drop-generic.)\n\n The code paths to compact multiple reftable files have been updated\n to correctly deal with multiple compaction triggering at the same\n time.\n source: \n\n\n* ps/submodule-ref-format (2024-08-08) 8 commits\n (merged to 'next' on 2024-08-09 at 2b17964809)\n + object: fix leaking packfiles when closing object store\n + submodule: fix leaking seen submodule names\n + submodule: fix leaking fetch tasks\n + builtin/submodule: allow \"add\" to use different ref storage format\n + refs: fix ref storage format for submodule ref stores\n + builtin/clone: propagate ref storage format to submodules\n + builtin/submodule: allow cloning with different ref storage format\n + git-submodule.sh: break overly long command lines\n\n Support to specify ref backend for submodules has been enhanced.\n source: \n\n\n* rs/t-example-simplify (2024-07-30) 1 commit\n (merged to 'next' on 2024-08-08 at edeb01c38e)\n + t-example-decorate: remove test messages\n\n Unit test simplification.\n source: <5c838884-b606-465a-8f7e-ab760ddadef8@web.de>\n\n\n* xx/diff-tree-remerge-diff-fix (2024-08-09) 1 commit\n (merged to 'next' on 2024-08-09 at cabe67c0d1)\n + diff-tree: fix crash when used with --remerge-diff\n (this branch is used by jc/range-diff-lazy-setup.)\n\n \"git rev-list ... | git diff-tree -p --remerge-diff --stdin\" should\n behave more or less like \"git log -p --remerge-diff\" but instead it\n crashed, forgetting to prepare a temporary object store needed.\n source: \n\n--------------------------------------------------\n[New Topics]\n\n* jc/how-to-maintain-updates (2024-08-14) 1 commit\n (merged to 'next' on 2024-08-15 at 20ebc08e74)\n + howto-maintain: mention preformatted docs\n\n Doc updates.\n\n Will merge to 'master'.\n source: \n\n\n* ah/git-prompt-portability (2024-08-15) 8 commits\n - git-prompt: support custom 0-width PS1 markers\n - git-prompt: ta-da! document usage in other shells\n - git-prompt: don't use shell $'...'\n - git-prompt: add some missing quotes\n - git-prompt: replace [[...]] with standard code\n - git-prompt: don't use shell arrays\n - git-prompt: fix uninitialized variable\n - git-prompt: use here-doc instead of here-string\n\n The command line prompt support used to be littered with bash-isms,\n which has been corrected to work with more shells.\n\n Will merge to 'next'?\n source: \n\n\n* jk/apply-patch-mode-check-fix (2024-08-15) 1 commit\n (merged to 'next' on 2024-08-15 at 8e077b7875)\n + t4129: fix racy index when calling chmod after git-add\n\n Test fix.\n\n Will merge to 'master'.\n source: <20240815153007.GA1477220@coredump.intra.peff.net>\n\n\n* ps/reftable-drop-generic (2024-08-15) 16 commits\n - reftable/generic: drop interface\n - t/helper: refactor to not use `struct reftable_table`\n - t/helper: use `hash_to_hex_algop()` to print hashes\n - t/helper: inline printing of reftable records\n - t/helper: inline `reftable_table_print()`\n - t/helper: inline `reftable_stack_print_directory()`\n - t/helper: inline `reftable_reader_print_file()`\n - t/helper: inline `reftable_dump_main()`\n - reftable/dump: drop unused `compact_stack()`\n - reftable/generic: move generic iterator code into iterator interface\n - reftable/iter: drop double-checking logic\n - reftable/stack: open-code reading refs\n - reftable/merged: stop using generic tables in the merged table\n - reftable/merged: rename `reftable_new_merged_table()`\n - reftable/merged: expose functions to initialize iterators\n - Merge branch 'ps/reftable-stack-compaction' into ps/reftable-drop-generic\n\n The code in the reftable library has been cleaned up by discarding\n unused \"generic\" interface.\n\n Needs review.\n source: \n\n\n* ps/hash-and-ref-format-from-config (2024-08-16) 5 commits\n - setup: make ref storage format configurable via config\n - setup: make object format configurable via config\n - setup: merge configuration of repository formats\n - t0001: delete repositories when object format tests finish\n - t0001: exercise initialization with ref formats more thoroughly\n\n The default object hash and ref backend format used to be settable\n only with explicit command line option to \"git init\" and\n environment variables, but now they can be configured in the user's\n global and system wide configuration.\n\n Will merge to 'next'.\n source: \n\n\n* tb/pseudo-merge-bitmap-fixes (2024-08-15) 8 commits\n - pseudo-merge.c: ensure pseudo-merge groups are closed\n - pseudo-merge.c: do not generate empty pseudo-merge commits\n - t/t5333-pseudo-merge-bitmaps.sh: demonstrate empty pseudo-merge groups\n - pack-bitmap-write.c: select pseudo-merges even for small bitmaps\n - pack-bitmap: drop redundant args from `bitmap_writer_finish()`\n - pack-bitmap: drop redundant args from `bitmap_writer_build()`\n - pack-bitmap: drop redundant args from `bitmap_writer_build_type_index()`\n - pack-bitmap: initialize `bitmap_writer_init()` with packing_data\n (this branch is used by tb/incremental-midx-part-2.)\n\n We created a useless pseudo-merge reachability bitmap that is about\n 0 commits, and attempted to include commits that are not in packs,\n which made no sense. These bugs have been corrected.\n\n Will merge to 'next'.\n source: \n\n\n* tb/incremental-midx-part-2 (2024-08-15) 15 commits\n - midx: implement writing incremental MIDX bitmaps\n - pack-bitmap.c: use `ewah_or_iterator` for type bitmap iterators\n - pack-bitmap.c: keep track of each layer's type bitmaps\n - ewah: implement `struct ewah_or_iterator`\n - pack-bitmap.c: apply pseudo-merge commits with incremental MIDXs\n - pack-bitmap.c: compute disk-usage with incremental MIDXs\n - pack-bitmap.c: teach `rev-list --test-bitmap` about incremental MIDXs\n - pack-bitmap.c: support bitmap pack-reuse with incremental MIDXs\n - pack-bitmap.c: teach `show_objects_for_type()` about incremental MIDXs\n - pack-bitmap.c: teach `bitmap_for_commit()` about incremental MIDXs\n - pack-bitmap.c: open and store incremental bitmap layers\n - pack-revindex: prepare for incremental MIDX bitmaps\n - Documentation: describe incremental MIDX bitmaps\n - Merge branch 'tb/pseudo-merge-bitmap-fixes' into tb/incremental-midx-part-2\n - Merge branch 'tb/incremental-midx-part-1' into tb/incremental-midx-part-2\n (this branch uses tb/incremental-midx-part-1 and tb/pseudo-merge-bitmap-fixes.)\n\n Incremental updates of multi-pack index files.\n\n source: \n\n\n* mt/rebase-x-quiet (2024-08-15) 1 commit\n - rebase -x: don't print \"Executing:\" msgs with --quiet\n\n \"git rebase -x --quiet\" was not quiet, which was corrected.\n\n Expecting a reroll.\n cf. \n source: <767ea219e3365303535c8b5f0d8eadb28b5e872e.1723778779.git.matheus.tavb@gmail.com>\n\n\n* ps/stash-keep-unrack-empty-fix (2024-08-16) 1 commit\n - builtin/stash: fix `--keep-index --include-untracked` with empty HEAD\n\n A corner case bug in \"git stash\" was fixed.\n\n Will merge to 'next'.\n source: <6067675b5edf36e2eb28e98119a1c02d0a7ae670.1723804926.git.ps@pks.im>\n\n--------------------------------------------------\n[Stalled]\n\n* pp/add-parse-range-unit-test (2024-05-27) 1 commit\n - apply: add unit tests for parse_range\n\n A unit test for code that parses the hunk offset and length from a\n patch fragment header as been added.\n\n Expecting a reroll.\n cf. \n source: \n\n--------------------------------------------------\n[Cooking]\n\n* gt/unit-test-urlmatch-normalization (2024-08-14) 1 commit\n - t: migrate t0110-urlmatch-normalization to the new framework\n\n Another rewrite of test.\n\n Comments?\n source: <20240814142057.94671-1-shyamthakkar001@gmail.com>\n\n\n* jk/midx-unused-fix (2024-08-13) 1 commit\n (merged to 'next' on 2024-08-14 at 2ec51e52e1)\n + midx: drop unused parameters from add_midx_to_chain()\n (this branch uses tb/incremental-midx-part-1.)\n\n Code clean-up in the base topic.\n\n Will merge to 'master'.\n source: \n\n\n* ps/bundle-outside-repo-fix (2024-08-13) 2 commits\n (merged to 'next' on 2024-08-15 at 3b9ea8a38a)\n + bundle: default to SHA1 when reading bundle headers\n + builtin/bundle: have unbundle check for repo before opening its bundle\n\n \"git bundle unbundle\" outside a repository triggered a BUG()\n unnecessarily, which has been corrected.\n\n Will merge to 'master'.\n source: \n\n\n* ps/clar-unit-test (2024-08-16) 9 commits\n - t/unit-tests: convert ctype tests to use clar\n - t/unit-tests: convert strvec tests to use clar\n - Makefile: wire up the clar unit testing framework\n - Makefile: do not use sparse on third-party sources\n - Makefile: make hdr-check depend on generated headers\n - Makefile: fix sparse dependency on GENERATED_H\n - t/clar: fix compatibility with NonStop\n - t: import the clar unit testing framework\n - t: do not pass GIT_TEST_OPTS to unit tests with prove\n\n Import clar unit tests framework libgit2 folks invented for our\n use.\n\n Needs to decide how to fill feature gap with our home-grown one\n cf. \n source: \n\n\n* ps/maintenance-detach-fix (2024-08-16) 7 commits\n - run-command: fix detaching when running auto maintenance\n - builtin/maintenance: add a `--detach` flag\n - builtin/gc: add a `--detach` flag\n - builtin/gc: stop processing log file on signal\n - builtin/gc: fix leaking config values\n - builtin/gc: refactor to read config into structure\n - config: fix constness of out parameter for `git_config_get_expiry()`\n\n Allow maintance tasks other than \"gc\" to properly go background\n when \"git maintenance\" run them.\n\n Will merge to 'next'.\n source: \n\n\n* jk/send-email-translate-aliases (2024-08-15) 4 commits\n - fixup! send-email: teach git send-email option to translate aliases\n - send-email: teach git send-email option to translate aliases\n - t9001-send-email.sh: update alias list used for pine test\n - t9001-send-email.sh: fix quoting for mailrc --dump-aliases test\n\n \"git send-email\" learned \"--translate-aliases\" option that reads\n addresses from the standard input and emits the result of applying\n aliases on them to the standard output.\n\n Will merge to 'next' after squashing the fix in.\n source: <20240813-jk-translate-alias-send-email-v2-0-912db4eb6846@gmail.com>\n\n\n* cp/unit-test-reftable-block (2024-08-14) 10 commits\n - t-reftable-block: add tests for index blocks\n - t-reftable-block: add tests for obj blocks\n - t-reftable-block: add tests for log blocks\n - t-reftable-block: remove unnecessary variable 'j'\n - t-reftable-block: use xstrfmt() instead of xstrdup()\n - t-reftable-block: use block_iter_reset() instead of block_iter_close()\n - t-reftable-block: use reftable_record_key() instead of strbuf_addstr()\n - t-reftable-block: use reftable_record_equal() instead of check_str()\n - t-reftable-block: release used block reader\n - t: move reftable/block_test.c to the unit testing framework\n\n Another test for reftable library ported to the unit test framework.\n\n Needs Review.\n source: <20240814121122.4642-1-chandrapratap3519@gmail.com>\n\n\n* jc/tests-no-useless-tee (2024-08-08) 1 commit\n (merged to 'next' on 2024-08-12 at 188e777e16)\n + tests: drop use of 'tee' that hides exit status\n\n Test fixes.\n\n Will merge to 'master'.\n source: \n\n\n* js/libgit-rust (2024-08-09) 5 commits\n - cgit: add higher-level cgit crate\n - config: add git_configset_alloc() and git_configset_clear_and_free()\n - cgit-sys: add repo initialization and config access\n - cgit-sys: introduce Rust wrapper for libgit.a\n - common-main: split init and exit code into new files\n\n An rust binding to libgit.a functions has been introduced.\n\n Inviting further comments.\n source: \n\n\n* jc/grammo-fixes (2024-08-09) 2 commits\n (merged to 'next' on 2024-08-15 at 111d5f5c13)\n + doc: grammofix in git-diff-tree\n + tutorial: grammofix\n\n Doc updates.\n\n Will merge to 'master'.\n source: \n\n\n* jc/range-diff-lazy-setup (2024-08-09) 2 commits\n - remerge-diff: clean up temporary objdir at a central place\n - remerge-diff: lazily prepare temporary objdir on demand\n\n Code clean-up.\n\n Comments?\n source: \n\n\n* jc/too-many-arguments (2024-08-06) 4 commits\n - miscellaneous: avoid \"too many arguments\"\n - notes: avoid \"too many arguments\"\n - cat-file: avoid \"too many arguments\"\n - refs: avoid \"too many arguments\"\n\n Error message clarification.\n\n On hold.\n source: <20240806003539.3292562-1-gitster@pobox.com>\n\n\n* ps/leakfixes-part-4 (2024-08-14) 23 commits\n - builtin/diff: free symmetric diff members\n - diff: free state populated via options\n - builtin/log: fix leak when showing converted blob contents\n - userdiff: fix leaking memory for configured diff drivers\n - builtin/format-patch: fix various trivial memory leaks\n - diff: fix leak when parsing invalid ignore regex option\n - unpack-trees: clear index when not propagating it\n - sequencer: release todo list on error paths\n - merge-ort: unconditionally release attributes index\n - builtin/fast-export: plug leaking tag names\n - builtin/fast-export: fix leaking diff options\n - builtin/fast-import: plug trivial memory leaks\n - builtin/notes: fix leaking `struct notes_tree` when merging notes\n - builtin/rebase: fix leaking `commit.gpgsign` value\n - config: fix leaking comment character config\n - submodule-config: fix leaking name entry when traversing submodules\n - read-cache: fix leaking hashfile when writing index fails\n - bulk-checkin: fix leaking state TODO\n - object-name: fix leaking symlink paths in object context\n - object-file: fix memory leak when reading corrupted headers\n - git: fix leaking system paths\n - remote: plug memory leak when aliasing URLs\n - Merge branch 'ps/leakfixes-part-3' into ps/leakfixes-part-4\n\n More leak fixes.\n\n Will merge to 'next'.\n source: \n\n\n* cp/unit-test-reftable-readwrite (2024-08-13) 4 commits\n - t-reftable-readwrite: add test for known error\n - t-reftable-readwrite: use 'for' in place of infinite 'while' loops\n - t-reftable-readwrite: use free_names() instead of a for loop\n - t: move reftable/readwrite_test.c to the unit testing framework\n\n Will merge to 'next'.\n source: <20240813144440.4602-1-chandrapratap3519@gmail.com>\n\n\n* ps/config-wo-the-repository (2024-08-13) 21 commits\n - config: hide functions using `the_repository` by default\n - global: prepare for hiding away repo-less config functions\n - config: don't depend on `the_repository` with branch conditions\n - config: don't have setters depend on `the_repository`\n - config: pass repo to functions that rename or copy sections\n - config: pass repo to `git_die_config()`\n - config: pass repo to `git_config_get_expiry_in_days()`\n - config: pass repo to `git_config_get_expiry()`\n - config: pass repo to `git_config_get_max_percent_split_change()`\n - config: pass repo to `git_config_get_split_index()`\n - config: pass repo to `git_config_get_index_threads()`\n - config: expose `repo_config_clear()`\n - config: introduce missing setters that take repo as parameter\n - path: hide functions using `the_repository` by default\n - path: stop relying on `the_repository` in `worktree_git_path()`\n - path: stop relying on `the_repository` when reporting garbage\n - hooks: remove implicit dependency on `the_repository`\n - editor: do not rely on `the_repository` for interactive edits\n - path: expose `do_git_common_path()` as `repo_common_pathv()`\n - path: expose `do_git_path()` as `repo_git_pathv()`\n - Merge branch 'ps/refs-wo-the-repository' into ps/config-wo-the-repository\n\n Use of API functions that implicitly depend on the_repository\n object in the config subsystem has been rewritten to pass a\n repository object through the callchain.\n\n Will merge to 'next'.\n source: \n\n\n* ps/transport-leakfix-test-updates (2024-08-08) 1 commit\n (merged to 'next' on 2024-08-12 at ee80dbc4f6)\n + transport: mark more tests leak-free\n\n Test updates.\n\n Will merge to 'master'.\n source: \n\n\n* ds/for-each-ref-is-base (2024-08-14) 4 commits\n - p1500: add is-base performance tests\n - for-each-ref: add 'is-base' token\n - commit: add gentle reference lookup method\n - commit-reach: add get_branch_base_for_tip\n\n 'git for-each-ref' learned a new \"--format\" atom to find the branch\n that the history leading to a given commit \"%(is-base:)\" is\n likely based on.\n\n Comments?\n source: \n\n\n* sj/ref-fsck (2024-08-08) 9 commits\n (merged to 'next' on 2024-08-09 at 3bde10da94)\n + fsck: add ref name check for files backend\n + files-backend: add unified interface for refs scanning\n + builtin/refs: add verify subcommand\n + refs: set up ref consistency check infrastructure\n + fsck: add refs report function\n + fsck: add a unified interface for reporting fsck messages\n + fsck: make \"fsck_error\" callback generic\n + fsck: rename objects-related fsck error functions\n + fsck: rename \"skiplist\" to \"skip_oids\"\n\n \"git fsck\" infrastructure has been taught to also check the sanity\n of the ref database, in addition to the object database.\n\n Will merge to 'master'.\n source: \n\n\n* cc/promisor-remote-capability (2024-07-31) 4 commits\n - promisor-remote: check advertised name or URL\n - Add 'promisor-remote' capability to protocol v2\n - strbuf: refactor strbuf_trim_trailing_ch()\n - version: refactor strbuf_sanitize()\n\n The v2 protocol learned to allow the server to advertise possible\n promisor remotes, and the client to respond with what promissor\n remotes it uses, so that the server side can omit objects that the\n client can lazily obtain from these other promissor remotes.\n\n Comments?\n source: <20240731134014.2299361-1-christian.couder@gmail.com>\n\n\n* tb/incremental-midx-part-1 (2024-08-06) 19 commits\n (merged to 'next' on 2024-08-12 at 92ec55fd49)\n + midx: implement support for writing incremental MIDX chains\n + t/t5313-pack-bounds-checks.sh: prepare for sub-directories\n + t: retire 'GIT_TEST_MULTI_PACK_INDEX_WRITE_BITMAP'\n + midx: implement verification support for incremental MIDXs\n + midx: support reading incremental MIDX chains\n + midx: teach `midx_fanout_add_midx_fanout()` about incremental MIDXs\n + midx: teach `midx_preferred_pack()` about incremental MIDXs\n + midx: teach `midx_contains_pack()` about incremental MIDXs\n + midx: remove unused `midx_locate_pack()`\n + midx: teach `fill_midx_entry()` about incremental MIDXs\n + midx: teach `nth_midxed_offset()` about incremental MIDXs\n + midx: teach `bsearch_midx()` about incremental MIDXs\n + midx: introduce `bsearch_one_midx()`\n + midx: teach `nth_bitmapped_pack()` about incremental MIDXs\n + midx: teach `nth_midxed_object_oid()` about incremental MIDXs\n + midx: teach `prepare_midx_pack()` about incremental MIDXs\n + midx: teach `nth_midxed_pack_int_id()` about incremental MIDXs\n + midx: add new fields for incremental MIDX chains\n + Documentation: describe incremental MIDX format\n (this branch is used by jk/midx-unused-fix and tb/incremental-midx-part-2.)\n\n Incremental updates of multi-pack index files.\n\n Will merge to 'master'.\n source: \n\n\n* ja/doc-synopsis-markup (2024-08-12) 3 commits\n - doc: apply synopsis simplification on git-clone and git-init\n - doc: update the guidelines to reflect the current formatting rules\n - doc: introduce a synopsis custom paragraph attribute\n\n The way AsciiDoc is used for SYNOPSIS part of the manual pages has\n been revamped. The sources, at least for the simple cases, got\n vastly pleasant to work with.\n\n Comments?\n source: \n\n\n* tc/fetch-bundle-uri (2024-07-24) 3 commits\n - fetch: use bundle URIs when having creationToken heuristic\n - transport: introduce transport_has_remote_bundle_uri()\n - clone: remove double bundle list clear code\n\n Allow \"git fetch\" take advantage of bundleURI feature.\n\n Expecting a reroll or retraction.\n source: \n\n\n* ag/git-svn-global-ignores (2024-08-14) 3 commits\n (merged to 'next' on 2024-08-15 at b8332fe306)\n + git-svn: mention `svn:global-ignores` in help+docs\n (merged to 'next' on 2024-08-08 at 3ba5e164a6)\n + git-svn: use `svn:global-ignores` to create .gitignore\n + git-svn: add public property `svn:global-ignores`\n\n \"git svn\" has been taught about svn:global-ignores property\n recent versions of Subversion has.\n\n Will merge to 'master'.\n source: \n source: \n\n\n* ew/cat-file-optim (2024-07-15) 10 commits\n - cat-file: use writev(2) if available\n - cat-file: batch_write: use size_t for length\n - cat-file: batch-command uses content_limit\n - object_info: content_limit only applies to blobs\n - packfile: packed_object_info avoids packed_to_object_type\n - cat-file: use delta_base_cache entries directly\n - packfile: inline cache_or_unpack_entry\n - packfile: fix off-by-one in content_limit comparison\n - packfile: allow content-limit for cat-file\n - packfile: move sizep computation\n\n \"git cat-file --batch\" has been optimized.\n\n Expecting a reroll.\n cf. \n source: <20240715003519.2671385-1-e@80x24.org>\n\n\n* rs/unit-tests-test-run (2024-07-30) 6 commits\n (merged to 'next' on 2024-08-12 at 9df4336877)\n + t-strvec: use if_test\n + t-reftable-basics: use if_test\n + t-ctype: use if_test\n + unit-tests: add if_test\n + unit-tests: show location of checks outside of tests\n + t0080: use here-doc test body\n\n Unit-test framework has learned a simple control structure to allow\n embedding test statements in-line instead of having to create a new\n function to contain them.\n\n Will merge to 'master'.\n source: <077a178e-eb30-45ff-b653-a514bfd33077@web.de>\n"},{"id":"501288","messageId":"b6e3763d-945f-fdf7-e620-cd26b8c72419@gmx.de","threadId":"61962","inReplyTo":"xmqqwmkgjomp.fsf@gitster.g","subject":"v2.46.1? was Re: What's cooking in git.git (Aug 2024, #06; Fri, 16)","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2024-08-19T16:49:07Z","receivedAt":"2024-08-19T16:49:11Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Junio,\n\nOn Fri, 16 Aug 2024, Junio C Hamano wrote:\n\n> Here are the topics that have been cooking in my tree. Commits\n> prefixed with '+' are in 'next' (being in 'next' is a sign that a\n> topic is stable enough to be used and are candidate to be in a\n> future release). Commits prefixed with '-' are only in 'seen', and\n> aren't considered \"accepted\" at all and may be annotated with an URL\n> to a message that raises issues but they are no means exhaustive. A\n> topic without enough support may be discarded after a long period of\n> no activity (of course they can be resubmit when new interests\n> arise).\n>\n> Copies of the source code to Git live in many repositories, and the\n> following is a list of the ones I push into or their mirrors. Some\n> repositories have only a subset of branches.\n\nI frequently look at these two paragraphs in the What's cooking mails, or\nmore specifically: at a paragraph inserted between these two occasionally,\nto get hints about imminent maintenance versions (to allow me to better\nprepare for them such as keeping back component updates in Git for Windows\nthat strike me as needing some exercise before being released in an\nofficial version).\n\nAbout 2.5h after sending the quoted mail, it seems that the `maint` branch\nwas updated with a hint that you plan on releasing a v2.46.1.\n\nCould I ask you what your plans are regarding v2.46.1 so that I don't\nexercise my weak fortune-telling abilities that would shock Sybill\nTrelawney?\n\nThank you,\nJohannes\n"},{"id":"501297","messageId":"xmqqplq4e31c.fsf@gitster.g","threadId":"61962","inReplyTo":"b6e3763d-945f-fdf7-e620-cd26b8c72419@gmx.de","subject":"Re: v2.46.1? was Re: What's cooking in git.git (Aug 2024, #06; Fri, 16)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2024-08-19T19:16:47Z","receivedAt":"2024-08-19T19:16:53Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Schindelin writes:\n\n> I frequently look at these two paragraphs in the What's cooking mails, or\n> more specifically: at a paragraph inserted between these two occasionally,\n> to get hints about imminent maintenance versions (to allow me to better\n> prepare for them such as keeping back component updates in Git for Windows\n> that strike me as needing some exercise before being released in an\n> official version).\n>\n> About 2.5h after sending the quoted mail, it seems that the `maint` branch\n> was updated with a hint that you plan on releasing a v2.46.1.\n\nThere is no immediate need for it and 2.46.1 does not even have to\nhappen. Just a grab bag of topics that are safe and are already on\ntrack for 2.47 are kept in case we accumulate enough of them.\n\n"},{"id":"501390","messageId":"7fcc8d92-d60b-2249-233d-7ce99ba96565@gmx.de","threadId":"61962","inReplyTo":"xmqqplq4e31c.fsf@gitster.g","subject":"Re: v2.46.1? was Re: What's cooking in git.git (Aug 2024, #06; Fri, 16)","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2024-08-20T20:15:15Z","receivedAt":"2024-08-20T20:15:22Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Junio,\n\nOn Mon, 19 Aug 2024, Junio C Hamano wrote:\n\n> Johannes Schindelin writes:\n>\n> > I frequently look at these two paragraphs in the What's cooking mails, or\n> > more specifically: at a paragraph inserted between these two occasionally,\n> > to get hints about imminent maintenance versions (to allow me to better\n> > prepare for them such as keeping back component updates in Git for Windows\n> > that strike me as needing some exercise before being released in an\n> > official version).\n> >\n> > About 2.5h after sending the quoted mail, it seems that the `maint` branch\n> > was updated with a hint that you plan on releasing a v2.46.1.\n>\n> There is no immediate need for it and 2.46.1 does not even have to\n> happen. Just a grab bag of topics that are safe and are already on\n> track for 2.47 are kept in case we accumulate enough of them.\n\nThank you for the clarification. I am a fan of getting things into the\n`maint` branch early, so I like what I am reading here.\n\nCiao,\nJohannes\n"},{"id":"501394","messageId":"xmqqy14r53lx.fsf@gitster.g","threadId":"61962","inReplyTo":"7fcc8d92-d60b-2249-233d-7ce99ba96565@gmx.de","subject":"Re: v2.46.1? was Re: What's cooking in git.git (Aug 2024, #06; Fri, 16)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2024-08-20T20:41:30Z","receivedAt":"2024-08-20T20:41:41Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Schindelin writes:\n\n>> There is no immediate need for it and 2.46.1 does not even have to\n>> happen. Just a grab bag of topics that are safe and are already on\n>> track for 2.47 are kept in case we accumulate enough of them.\n>\n> Thank you for the clarification. I am a fan of getting things into the\n> `maint` branch early, so I like what I am reading here.\n\nMerging early, often, and in small batches will in theory make the\nprocess safer by giving us more chance to see things unexpectedly\nbreak, and that is why I too prefer it, but that is only true if\nenough people are paying attention to the branch. I however have a\nfeeling that nobody uses 'maint' UNTIL the tip of it is tagged,\nthough..\n\n\n"}]}