From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-3.5 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from sy.mirrors.kernel.org (sy.mirrors.kernel.org [IPv6:2604:1380:40f1:3f00::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 279641F44D for ; Sat, 16 Mar 2024 00:28:24 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=pobox.com header.i=@pobox.com header.a=rsa-sha256 header.s=sasl header.b=lYbdVzdU; dkim-atps=neutral Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sy.mirrors.kernel.org (Postfix) with ESMTPS id B75BBB212CE for ; Sat, 16 Mar 2024 00:28:21 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 924D2A21; Sat, 16 Mar 2024 00:28:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=pobox.com header.i=@pobox.com header.b="lYbdVzdU" Received: from pb-smtp1.pobox.com (pb-smtp1.pobox.com [64.147.108.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id ED0BB360 for ; Sat, 16 Mar 2024 00:28:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=64.147.108.70 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1710548893; cv=none; b=uVTKBpOazID9aTRFKwgWomjFDo0vspx4kLcesl6Cd/6pBuAnLBO/Eq9WgJi/d4b/kPhKYUVCLq5dDp/mGzq/jSGO0ld2581SMxbM2RgafFzCQiOwYw5tmzNNq7tAgzSKhqxmhBRY+AKM//lyqIb0qnLjR96Jl+vfnfnSk0twmw0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1710548893; c=relaxed/simple; bh=uY/RPa2ty/+KWAVHUSzxsFHf8lF+7I1l21nm8lh9BgU=; h=From:To:Subject:Date:Message-ID:MIME-Version:Content-Type; b=PLXy3YsgoqYIQSmVTfnyjMubHaFWtXecScVgGG+XhwjeiiumlJtTCwqKw4CH4x9V3euyivF0TkRmK2D/S4ccFN1RFjT3+sPh3aNKpxGrW2vNGTKLWTRQfU4RJBhTiQapJKzMhCNNSfsrqcL4qZbjkEgelB9/Zkyti/aIDrm4PbM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=pobox.com; spf=pass smtp.mailfrom=pobox.com; dkim=pass (1024-bit key) header.d=pobox.com header.i=@pobox.com header.b=lYbdVzdU; arc=none smtp.client-ip=64.147.108.70 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=pobox.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=pobox.com Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 229621E6299; Fri, 15 Mar 2024 20:26:15 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=from:to :subject:date:message-id:mime-version:content-type; s=sasl; bh=u Y/RPa2ty/+KWAVHUSzxsFHf8lF+7I1l21nm8lh9BgU=; b=lYbdVzdU9RaGfX8v/ FQyGRuC6Lw9pcmy+fGp9iRR4xn2w+FT9PKi+7z/7vC0D8ONy86+rqAhO2Ov0njxV hzsgZapry4VxpM6TJ0w+tsfgCoB0MHsjPPBmuuBcm15oR2ZCjmJUMaS5+dr1MC9O P9FHm0PK05DPRrFoJxlLxKKivE= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 1B0DB1E6298; Fri, 15 Mar 2024 20:26:15 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.125.185.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 49D1C1E6297; Fri, 15 Mar 2024 20:26:14 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: git@vger.kernel.org Subject: What's cooking in git.git (Mar 2024, #04; Fri, 15) X-master-at: 2953d95d402b6bff1a59c4712f4d46f1b9ea137f X-next-at: cdc2e80fe5f5dd8f872f21cdcd608126da6ccc7e Date: Fri, 15 Mar 2024 17:26:13 -0700 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Precedence: bulk X-Mailing-List: git@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: CC25D4C6-E32B-11EE-AE30-78DCEB2EC81B-77302942!pb-smtp1.pobox.com Here are the topics that have been cooking in my tree. Commits prefixed with '+' are in 'next' (being in 'next' is a sign that a topic is stable enough to be used and are candidate to be in a future release). Commits prefixed with '-' are only in 'seen', and aren't considered "accepted" at all and may be annotated with an URL to a message that raises issues but they are no means exhaustive. A topic without enough support may be discarded after a long period of no activity (of course they can be resubmit when new interests arise). 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. With maint, master, next, seen, todo: git://git.kernel.org/pub/scm/git/git.git/ git://repo.or.cz/alt-git.git/ https://kernel.googlesource.com/pub/scm/git/git/ https://github.com/git/git/ https://gitlab.com/git-vcs/git/ With all the integration branches and topics broken out: https://github.com/gitster/git/ Even though the preformatted documentation in HTML and man format are not sources, they are published in these repositories for convenience (replace "htmldocs" with "manpages" for the manual pages): git://git.kernel.org/pub/scm/git/git-htmldocs.git/ https://github.com/gitster/git-htmldocs.git/ Release tarballs are available at: https://www.kernel.org/pub/software/scm/git/ -------------------------------------------------- [Graduated to 'master'] * ag/t0010-modernize (2024-03-05) 1 commit (merged to 'next' on 2024-03-07 at 38339abc2d) + tests: modernize the test script t0010-racy-git.sh GSoC practice to modernize a test script. source: * as/option-names-in-messages (2024-03-05) 4 commits (merged to 'next' on 2024-03-07 at 73ab51faba) + revision.c: trivial fix to message + builtin/clone.c: trivial fix of message + builtin/remote.c: trivial fix of error message + transport-helper.c: trivial fix of error message Error message updates. source: <20240216101647.28837-1-ash@kambanaria.org> * gt/core-bare-in-templates (2024-03-04) 1 commit (merged to 'next' on 2024-03-06 at e54ac5acf9) + setup: remove unnecessary variable Code simplification. source: <20240304151811.511780-1-shyamthakkar001@gmail.com> * hd/config-mak-os390 (2024-03-06) 1 commit (merged to 'next' on 2024-03-07 at 289d3ab691) + build: support z/OS (OS/390). Platform specific tweaks for OS/390 has been added to config.mak.uname. source: * jc/test-i18ngrep (2024-03-02) 1 commit (merged to 'next' on 2024-03-06 at 2c57ebc706) + test_i18ngrep: hard deprecate and forbid its use With release 2.44 we got rid of all uses of test_i18ngrep and there is no in-flight topic that adds a new use of it. Make a call to test_i18ngrep a hard failure, so that we can remove it at the end of this release cycle. source: * jc/xwrite-cleanup (2024-03-02) 3 commits (merged to 'next' on 2024-03-07 at 43e66f7e4d) + repack: check error writing to pack-objects subprocess + sideband: avoid short write(2) + unpack: replace xwrite() loop with write_in_full() Uses of xwrite() helper have been audited and updated for better error checking and simpler code. source: <20240302190348.3946569-1-gitster@pobox.com> * jh/fsmonitor-icase-corner-case-fix (2024-03-06) 14 commits (merged to 'next' on 2024-03-06 at 356eafea7e) + fsmonitor: support case-insensitive events + fsmonitor: refactor bit invalidation in refresh callback + fsmonitor: trace the new invalidated cache-entry count + fsmonitor: return invalidated cache-entry count on non-directory event + fsmonitor: remove custom loop from non-directory path handler + fsmonitor: return invalidated cache-entry count on directory event + fsmonitor: move untracked-cache invalidation into helper functions + fsmonitor: refactor untracked-cache invalidation + dir: create untracked_cache_invalidate_trimmed_path() + fsmonitor: refactor refresh callback for non-directory events + fsmonitor: clarify handling of directory events in callback helper + fsmonitor: refactor refresh callback on directory events + t7527: add case-insensitve test for FSMonitor + name-hash: add index_dir_find() FSMonitor client code was confused when FSEvents were given in a different case on a case-insensitive filesystem, which has been corrected. Acked-by: Patrick Steinhardt cf. source: * kh/branch-ref-syntax-advice (2024-03-05) 5 commits (merged to 'next' on 2024-03-07 at 914f01967b) + branch: advise about ref syntax rules + advice: use double quotes for regular quoting + advice: use backticks for verbatim + advice: make all entries stylistically consistent + t3200: improve test style When git refuses to create a branch because the proposed branch name is not a valid refname, an advice message is given to refer the user to exact naming rules. source: * kh/doc-commentchar-is-a-byte (2024-03-05) 1 commit (merged to 'next' on 2024-03-06 at 5941655c04) + config: document `core.commentChar` as ASCII-only The "core.commentChar" configuration variable only allows an ASCII character, which was not clearly documented, which has been corrected. source: <9633f9be5ddd9ab3df4b79ee934e1ed47e90bd1d.1709656683.git.code@khaugsbakk.name> * la/trailer-api (2024-03-01) 9 commits (merged to 'next' on 2024-03-06 at f119923ff6) + format_trailers_from_commit(): indirectly call trailer_info_get() + format_trailer_info(): move "fast path" to caller + format_trailers(): use strbuf instead of FILE + trailer_info_get(): reorder parameters + trailer: move interpret_trailers() to interpret-trailers.c + trailer: reorder format_trailers_from_commit() parameters + trailer: rename functions to use 'trailer' + shortlog: add test for de-duplicating folded trailers + trailer: free trailer_info _after_ all related usage Trailer API updates. Acked-by: Christian Couder cf. source: * ps/reftable-iteration-perf-part2 (2024-03-04) 13 commits (merged to 'next' on 2024-03-06 at e8ba314585) + refs/reftable: precompute prefix length + reftable: allow inlining of a few functions + reftable/record: decode keys in place + reftable/record: reuse refname when copying + reftable/record: reuse refname when decoding + reftable/merged: avoid duplicate pqueue emptiness check + reftable/merged: circumvent pqueue with single subiter + reftable/merged: handle subiter cleanup on close only + reftable/merged: remove unnecessary null check for subiters + reftable/merged: make subiters own their records + reftable/merged: advance subiter on subsequent iteration + reftable/merged: make `merged_iter` structure private + reftable/pq: use `size_t` to track iterator index (this branch is used by ps/reftable-reflog-iteration-perf.) The code to iterate over refs with the reftable backend has seen some optimization. source: * rj/complete-reflog (2024-03-03) 5 commits (merged to 'next' on 2024-03-06 at 0f1a25debc) + completion: reflog subcommands and options + completion: factor out __git_resolve_builtins + completion: introduce __git_find_subcommand + completion: reflog show + completion: reflog with implicit "show" The command line completion script (in contrib/) learned to complete "git reflog" better. source: * rj/complete-worktree-paths-fix (2024-02-27) 1 commit (merged to 'next' on 2024-03-06 at b6ba949383) + completion: fix __git_complete_worktree_paths The logic to complete the command line arguments to "git worktree" subcommand (in contrib/) has been updated to correctly honor things like "git -C dir" etc. source: * so/clean-dry-run-without-force (2024-03-04) 2 commits (merged to 'next' on 2024-03-06 at ccf2e123be) + clean: further clean-up of implementation around "--force" + clean: improve -n and -f implementation and documentation The implementation in "git clean" that makes "-n" and "-i" ignore clean.requireForce has been simplified, together with the documentation. source: <87le6ziqzb.fsf_-_@osv.gnss.ru> source: <20240303220600.2491792-1-gitster@pobox.com> * vm/t7301-use-test-path-helpers (2024-03-06) 1 commit (merged to 'next' on 2024-03-07 at e638654635) + t7301: use test_path_is_(missing|file) GSoC practice to replace "test -f" with "test_path_is_file". source: <20240304171732.64457-2-vincenzo.mezzela@gmail.com> -------------------------------------------------- [New Topics] * bb/iso-strict-utc (2024-03-13) 1 commit (merged to 'next' on 2024-03-14 at d2ac616873) + date: make "iso-strict" conforming for the UTC timezone The output format for dates "iso-strict" has been tweaked to show a time in the Zulu timezone with "Z" suffix, instead of "+00:00". Will merge to 'master'. source: <20240313225423.11373-1-dev+git@drbeat.li> * dg/user-manual-hash-example (2024-03-12) 1 commit (merged to 'next' on 2024-03-14 at 767800d3a7) + Documentation/user-manual.txt: example for generating object hashes User manual (the original one) update. Will merge to 'master'. source: <20240312104238.4920-2-dirk@gouders.net> * jc/show-untracked-false (2024-03-13) 2 commits - status: allow --untracked=false and friends - status: unify parsing of --untracked= and status.showUntrackedFiles The status.showUntrackedFiles configuration variable had a name that tempts users to set a Boolean value expressed in our usual "false", "off", and "0", but it only took "no". This has been corrected so "true" and its synonyms are taken as "normal", while "false" and its synonyms are taken as "no". Will merge to 'next'? source: <20240313173214.962532-1-gitster@pobox.com> * js/bugreport-no-suffix-fix (2024-03-14) 1 commit - bugreport.c: fix a crash in `git bugreport` with `--no-suffix` option "git bugreport --no-suffix" was not supported and instead segfaulted, which has been corrected. Will merge to 'next'? source: <9c6f3f5203ae26c501a5711e2610573130bfd550.1710388817.git.gitgitgadget@gmail.com> * jw/doc-show-untracked-files-fix (2024-03-13) 1 commit (merged to 'next' on 2024-03-14 at 091f64ad6c) + doc: status.showUntrackedFiles does not take "false" The status.showUntrackedFiles configuration variable was incorrectly documented to accept "false", which has been corrected. Will merge to 'master'. source: * ph/diff-src-dst-prefix-config (2024-03-15) 1 commit - diff: add diff.srcPrefix and diff.dstPrefix configuration variables "git diff" and friends learned two extra configuration variables. What's the status of this thing? source: <20240315010310.GA1901653@quokka> * ps/clone-with-includeif-onbranch (2024-03-12) 1 commit - t5601: exercise clones with "includeIf.*.onbranch" An additional test to demonstrate something I am not sure what. Waiting for a review response. cf. source: <0bede59a53862585c49bc635f82e44e983144a7f.1710246859.git.ps@pks.im> * bb/t0006-negative-tz-offset (2024-03-14) 1 commit (merged to 'next' on 2024-03-14 at 3f4751b6b2) + t0006: add more tests with a negative TZ offset More tests on showing time with negative TZ offset. Will merge to 'master'. source: <20240314085512.1827031-1-dev+git@drbeat.li> * rj/restore-plug-leaks (2024-03-14) 1 commit (merged to 'next' on 2024-03-15 at ac10ae7892) + checkout: plug some leaks in git-restore Leaks from "git restore" have been plugged. Will merge to 'master'. source: <64c1c3cc-51d7-4168-9731-4389889e1449@gmail.com> * bt/fuzz-config-parse (2024-03-15) 1 commit - fuzz: add fuzzer for config parsing A new fuzz target that exercises config parsing code. Will merge to 'next'? source: * ds/doc-config-reflow (2024-03-14) 1 commit - config.txt: perform some minor reformatting Reflow a paragraph in the documentation source without any effect to the formatted text. Comments? source: <97bdaf075bf5a68554cca1731eca78aff2662907.1710444774.git.dsimic@manjaro.org> * jc/index-pack-fsck-levels (2024-03-15) 1 commit - t5300: fix test_with_bad_commit() Test fix. Will merge to 'next'. source: * la/format-trailer-info (2024-03-15) 5 commits - trailer: finish formatting unification - trailer: begin formatting unification - format_trailer_info(): append newline for non-trailer lines - format_trailer_info(): drop redundant unfold_value() - format_trailer_info(): use trailer_item objects The code to format trailers have been cleaned up. Comments? source: * rs/config-comment (2024-03-15) 3 commits - config: allow tweaking whitespace between value and comment - config: fix --comment formatting - config: add --comment option to add a comment "git config" learned "--comment=" option to leave a comment immediately after the "variable = value" on the same line in the configuration file. Waiting for review response. cf. source: -------------------------------------------------- [Cooking] * jc/safe-implicit-bare (2024-03-11) 1 commit (merged to 'next' on 2024-03-14 at e8bdbed1a4) + setup: notice more types of implicit bare repositories Users with safe.bareRepository=explicit can still work from within $GIT_DIR of a seconary worktree (which resides at .git/worktrees/$name/) of the primary worktree without explicitly specifying the $GIT_DIR environment variable or the --git-dir= option. Will merge to 'master'. source: * pw/checkout-conflict-errorfix (2024-03-14) 5 commits - checkout: fix interaction between --conflict and --merge - checkout: cleanup --conflict=