From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS53758 23.128.96.0/24 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 0D9B51F5AE for ; Thu, 6 May 2021 05:37:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232838AbhEFFig (ORCPT ); Thu, 6 May 2021 01:38:36 -0400 Received: from pb-smtp2.pobox.com ([64.147.108.71]:53037 "EHLO pb-smtp2.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229622AbhEFFig (ORCPT ); Thu, 6 May 2021 01:38:36 -0400 Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 51851D4B9F; Thu, 6 May 2021 01:37:37 -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=j 8dQQl46gayKgD0+WzvJAquXPPefcVbuBvbExkZyNno=; b=WOEHM3rX1TRrmSamP CzK3sZ2WeImYVfHCkHgZJgPgqf/LaGxtZhyDTxclNAIv+msJMeAZITxqz/G2iraz kPN6GYFQeitCnNGoRdfml2Jp6ZvcLJdgIjQvSZtLZ7q4w0Ce9lwgx2/Ixkq4hAti Zz43UXfZGVmHnV9v/wjzjj4GUs= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 46C69D4B9E; Thu, 6 May 2021 01:37:37 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.74.119.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id AA2EED4B9D; Thu, 6 May 2021 01:37:36 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: git@vger.kernel.org Subject: What's cooking in git.git (May 2021, #01; Thu, 6) X-master-at: 7e391989789db82983665667013a46eabc6fc570 X-next-at: 1ce651569ca7e0a65f24af9c9548363d83d99866 Date: Thu, 06 May 2021 14:37:36 +0900 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: 2A0C9688-AE2D-11EB-AA5D-74DE23BA3BAF-77302942!pb-smtp2.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Here are the topics that have been cooking. Commits prefixed with '-' are only in 'seen' (formerly 'pu'---proposed updates) while commits prefixed with '+' are in 'next'. The ones marked with '.' do not appear in any of the integration branches, but I am still holding onto them. 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'] * ab/pathname-encoding-doc (2021-04-20) 1 commit (merged to 'next' on 2021-04-20 at a90562c59f) + doc: clarify the filename encoding in git diff Clarify that pathnames recorded in Git trees are most often (but not necessarily) encoded in UTF-8. * ds/maintenance-prefetch-fix (2021-04-16) 4 commits (merged to 'next' on 2021-04-16 at 0a1818e235) + maintenance: respect remote.*.skipFetchAll + maintenance: use 'git fetch --prefetch' + fetch: add --prefetch option + maintenance: simplify prefetch logic The prefetch task in "git maintenance" assumed that "git fetch" from any remote would fetch all its local branches, which would fetch too much if the user is interested in only a subset of branches there. * ds/sparse-index (2021-03-30) 21 commits (merged to 'next' on 2021-04-07 at f1290a7929) + p2000: add sparse-index repos + sparse-index: loose integration with cache_tree_verify() + cache-tree: integrate with sparse directory entries + sparse-checkout: disable sparse-index + sparse-checkout: toggle sparse index from builtin + sparse-index: add index.sparse config option + sparse-index: check index conversion happens + unpack-trees: allow sparse directories + submodule: sparse-index should not collapse links + sparse-index: convert from full to sparse + sparse-index: add 'sdir' index extension + sparse-checkout: hold pattern list in index + unpack-trees: ensure full index + test-tool: don't force full index + test-read-cache: print cache entries with --table + t1092: compare sparse-checkout to sparse-index + sparse-index: implement ensure_full_index() + sparse-index: add guard to ensure full index + t1092: clean up script quoting + t/perf: add performance test for sparse operations + sparse-index: design doc and format update (this branch is used by ds/sparse-index-protections and ds/status-with-sparse-index.) Both in-core and on-disk index has been updated to optionally omit individual entries and replace them with the tree object that corresponds to the directory that contains them when the "cone" mode of sparse checkout is in use. * ds/sparse-index-protections (2021-04-14) 26 commits (merged to 'next' on 2021-04-17 at f1c40f89ba) + name-hash: use expand_to_path() + sparse-index: expand_to_path() + name-hash: don't add directories to name_hash + revision: ensure full index + resolve-undo: ensure full index + read-cache: ensure full index + pathspec: ensure full index + merge-recursive: ensure full index + entry: ensure full index + dir: ensure full index + update-index: ensure full index + stash: ensure full index + rm: ensure full index + merge-index: ensure full index + ls-files: ensure full index + grep: ensure full index + fsck: ensure full index + difftool: ensure full index + commit: ensure full index + checkout: ensure full index + checkout-index: ensure full index + add: ensure full index + cache: move ensure_full_index() to cache.h + read-cache: expand on query into sparse-directory entry + *: remove 'const' qualifier for struct index_state + sparse-index: API protection strategy (this branch is used by ds/status-with-sparse-index; uses ds/sparse-index.) Builds on top of the sparse-index infrastructure to mark operations that are not ready to mark with the sparse index, causing them to fall back on fully-populated index that they always have worked with. * hn/refs-trace-errno (2021-04-12) 1 commit (merged to 'next' on 2021-04-20 at 0816e49d22) + refs: print errno for read_raw_ref if GIT_TRACE_REFS is set Show errno in the trace output in the error codepath that calls read_raw_ref method. * jk/promisor-optim (2021-04-13) 3 commits (merged to 'next' on 2021-04-15 at 41f303ef9b) + revision: avoid parsing with --exclude-promisor-objects + lookup_unknown_object(): take a repository argument + is_promisor_object(): free tree buffer after parsing (this branch is used by rs/repack-without-loosening-promised-objects.) Handling of "promisor packs" that allows certain objects to be missing and lazily retrievable has been optimized (a bit). * mt/parallel-checkout-part-2 (2021-04-19) 5 commits (merged to 'next' on 2021-04-20 at d4779b8864) + parallel-checkout: add design documentation + parallel-checkout: support progress displaying + parallel-checkout: add configuration options + parallel-checkout: make it truly parallel + unpack-trees: add basic support for parallel checkout (this branch is used by mt/parallel-checkout-part-3.) The checkout machinery has been taught to perform the actual write-out of the files in parallel when able. * mt/pkt-write-errors (2021-04-15) 1 commit (merged to 'next' on 2021-04-16 at 4a82d89ff3) + pkt-line: do not report packet write errors twice When packet_write() fails, we gave an extra error message unnecessarily, which has been corrected. * ow/push-quiet-set-upstream (2021-04-15) 1 commit (merged to 'next' on 2021-04-16 at 9466d4ef38) + transport: respect verbosity when setting upstream "git push --quiet --set-upstream" was not quiet when setting the upstream branch configuration, which has been corrected. * so/log-diff-merge (2021-04-16) 5 commits (merged to 'next' on 2021-04-17 at 6c1eba8ee3) + doc/diff-options: document new --diff-merges features + diff-merges: introduce log.diffMerges config variable + diff-merges: adapt -m to enable default diff format + diff-merges: refactor set_diff_merges() + diff-merges: introduce --diff-merges=on "git log" learned "--diff-merges=