global/git
1
0
Fork 0
mirror of https://github.com/git/git.git synced 2026-03-05 06:57:37 +01:00
Code Issues Packages Projects Releases Wiki Activity

What's cooking (2024/04 #01)

Browse Source
This commit is contained in:
Junio C Hamano
2024-04-01 11:38:22 -07:00
parent 1fbab3dc4d
commit 4b384fc611
1 changed files with 87 additions and 88 deletions
Download Patch File Download Diff File Expand all files Collapse all files

175
whats-cooking.txt
View File

@@ -1,10 +1,10 @@
To: git@vger.kernel.org
Subject: What's cooking in git.git (Mar 2024, #09; Thu, 28)
Subject: What's cooking in git.git (Apr 2024, #01; Mon, 1)
X-master-at: d6fd04375f9196f8b203d442f235bd96a1a068cc
X-next-at: 09a8706636d10c491176b8b1cd6519f7300911bf
Bcc: lwn@lwn.net, gitster@pobox.com
What's cooking in git.git (Mar 2024, #09; Thu, 28)
What's cooking in git.git (Apr 2024, #01; Mon, 1)
--------------------------------------------------
Here are the topics that have been cooking in my tree. Commits
@@ -27,7 +27,7 @@ With maint, master, next, seen, todo:
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/
https://gitlab.com/git-scm/git/
With all the integration branches and topics broken out:
@@ -46,101 +46,99 @@ Release tarballs are available at:
https://www.kernel.org/pub/software/scm/git/
--------------------------------------------------
[Graduated to 'master']
[New Topics]
* bt/fuzz-config-parse (2024-03-15) 1 commit
(merged to 'next' on 2024-03-21 at 6e9f331d68)
+ fuzz: add fuzzer for config parsing
* es/test-cron-safety (2024-03-31) 1 commit
- test-lib: fix non-functioning GIT_TEST_MAINT_SCHEDULER fallback
A new fuzz target that exercises config parsing code has been
added.
source: <pull.1692.v2.git.1710481652130.gitgitgadget@gmail.com>
The test script had an incomplete and ineffective attempt to avoid
clobbering the testing user's real crontab (and its equivalents),
which has been completed.
Will merge to 'next'.
source: <20240329222703.9343-1-ericsunshine@charter.net>
* eb/hash-transition (2023-10-02) 30 commits
(merged to 'next' on 2024-03-11 at 9cff2e4ab7)
+ t1016-compatObjectFormat: add tests to verify the conversion between objects
+ t1006: test oid compatibility with cat-file
+ t1006: rename sha1 to oid
+ test-lib: compute the compatibility hash so tests may use it
+ builtin/ls-tree: let the oid determine the output algorithm
+ object-file: handle compat objects in check_object_signature
+ tree-walk: init_tree_desc take an oid to get the hash algorithm
+ builtin/cat-file: let the oid determine the output algorithm
+ rev-parse: add an --output-object-format parameter
+ repository: implement extensions.compatObjectFormat
+ object-file: update object_info_extended to reencode objects
+ object-file-convert: convert commits that embed signed tags
+ object-file-convert: convert commit objects when writing
+ object-file-convert: don't leak when converting tag objects
+ object-file-convert: convert tag objects when writing
+ object-file-convert: add a function to convert trees between algorithms
+ object: factor out parse_mode out of fast-import and tree-walk into in object.h
+ cache: add a function to read an OID of a specific algorithm
+ tag: sign both hashes
+ commit: export add_header_signature to support handling signatures on tags
+ commit: convert mergetag before computing the signature of a commit
+ commit: write commits for both hashes
+ object-file: add a compat_oid_in parameter to write_object_file_flags
+ object-file: update the loose object map when writing loose objects
+ loose: compatibilty short name support
+ loose: add a mapping between SHA-1 and SHA-256 for loose objects
+ repository: add a compatibility hash algorithm
+ object-names: support input of oids in any supported hash
+ oid-array: teach oid-array to handle multiple kinds of oids
+ object-file-convert: stubs for converting from one object format to another
* gt/add-u-commit-i-pathspec-check (2024-03-29) 3 commits
- builtin/add: error out when passing untracked path with -u
- builtin/commit: error out when passing untracked path with -i
- read-cache: optionally collect pathspec matching info
Work to support a repository that work with both SHA-1 and SHA-256
hash algorithms has started.
source: <878r8l929e.fsf@gmail.froward.int.ebiederm.org>
"git add -u <pathspec>" and "git commit [-i] <pathspec>" did not
diagnose a pathspec element that did not match any files in certain
situations, unlike "git add <pathspec>" did.
Comments?
source: <20240318155219.494206-2-shyamthakkar001@gmail.com>
* jc/show-untracked-false (2024-03-13) 2 commits
(merged to 'next' on 2024-03-21 at 6d1f5603c6)
+ status: allow --untracked=false and friends
+ status: unify parsing of --untracked= and status.showUntrackedFiles
* jc/advice-sans-trailing-whitespace (2024-03-29) 1 commit
- advice: omit trailing whitespace
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".
source: <20240313173214.962532-1-gitster@pobox.com>
The "hint:" messages given by the advice mechanism, when given a
message with a blank line, left a line with trailing whitespace,
which has been cleansed.
Will merge to 'next'.
source: <xmqq4jcooddp.fsf@gitster.g>
* jk/drop-hg-to-git (2024-03-20) 1 commit
(merged to 'next' on 2024-03-21 at 603d614310)
+ contrib: drop hg-to-git script
* jt/reftable-geometric-compaction (2024-03-29) 3 commits
- reftable/stack: make segment end inclusive
- reftable/stack: use geometric table compaction
- reftable/stack: add env to disable autocompaction
Remove an ancient and not well maintained Hg-to-git migration
script from contrib/.
The strategy to compat multiple tables of reftables after many
operations accumulate many entries has been improved to avoid
accumulating too many tables uncollected.
Acked-by: Stelian Pop <stelian@popies.net>
cf. <37e4cd61-b370-437e-bd42-f98f47d3ad32@popies.net>
source: <20240320094824.GA2445978@coredump.intra.peff.net>
Will merge to 'next'?
cf. <Zfzd_yxeXWWTJdyP@tanuki>
source: <pull.1683.v3.git.1711685809.gitgitgadget@gmail.com>
* ph/diff-src-dst-prefix-config (2024-03-18) 2 commits
(merged to 'next' on 2024-03-21 at 96801520db)
+ diff.*Prefix: use camelCase in the doc and test titles
+ diff: add diff.srcPrefix and diff.dstPrefix configuration variables
* ds/typofix-core-config-doc (2024-03-31) 1 commit
- config: fix some small capitalization issues, as spotted
"git diff" and friends learned two extra configuration variables,
diff.srcPrefix and diff.dstPrefix.
source: <20240315010310.GA1901653@quokka>
source: <xmqq8r2ioh19.fsf@gitster.g>
Typofix.
Will merge to 'next'.
source: <26135b06c48565ee8ac6dcfc1ef5431511e6202c.1711918168.git.dsimic@manjaro.org>
* rs/t-prio-queue-fixes (2024-03-18) 2 commits
(merged to 'next' on 2024-03-21 at 0730741187)
+ t-prio-queue: check result array bounds
+ t-prio-queue: shorten array index message
* jc/checkout-detach-wo-tracking-report (2024-03-30) 1 commit
- checkout: omit "tracking" information on a detached HEAD
Test clean-up.
source: <9bf36cc8-ff27-44df-b2fb-9f959c781269@web.de>
"git checkout/switch --detach foo", after switching to the detached
HEAD state, gave the tracking information for the 'foo' branch,
which was pointless.
Comments?
source: <xmqqa5mfl7ud.fsf@gitster.g>
* rj/use-adv-if-enabled (2024-03-30) 3 commits
- add: use advise_if_enabled for ADVICE_ADD_EMBEDDED_REPO
- add: use advise_if_enabled for ADVICE_ADD_EMPTY_PATHSPEC
- add: use advise_if_enabled for ADVICE_ADD_IGNORED_FILE
Use advice_if_enabled() API to rewrite a simple pattern to
call advise() after checking advice_enabled().
Will merge to 'next'?
source: <46fba030-d7aa-49d2-88fa-e506850f7b6a@gmail.com>
* rs/mem-pool-size-t-safety (2024-03-31) 1 commit
- mem-pool: use st_add() in mem_pool_strvfmt()
size_t arithmetic safety.
Will merge to 'next'.
source: <bbe00b9e-64d8-4ec8-a2b9-2c6917c72dbd@web.de>
--------------------------------------------------
[New Topics]
[Cooking]
* ew/khash-to-khashl (2024-03-28) 3 commits
- khashl: fix ensemble lookups on empty table
@@ -172,7 +170,7 @@ Release tarballs are available at:
source: <cover.1711519925.git.ps@pks.im>
* rj/add-p-explicit-reshow (2024-03-28) 2 commits
* rj/add-p-explicit-reshow (2024-03-29) 2 commits
- add-patch: do not print hunks repeatedly
- add-patch: introduce 'p' in interactive-patch
@@ -181,10 +179,8 @@ Release tarballs are available at:
an additional action to explicitly ask to reshow the current hunk.
Will merge to 'next'?
source: <60d978d0-f69a-4b65-b4ba-d30dac8f112a@gmail.com>
source: <a9c515fe-6664-4b5d-abca-d88fdd32a883@gmail.com>
--------------------------------------------------
[Cooking]
* az/grep-group-error-message-update (2024-03-25) 1 commit
(merged to 'next' on 2024-03-27 at 567bf00ed4)
@@ -244,8 +240,9 @@ Release tarballs are available at:
source: <cover.1711398665.git.dsimic@manjaro.org>
* ja/doc-markup-updates (2024-03-25) 4 commits
- doc: git-clone: apply new documentation guidelines
* ja/doc-markup-updates (2024-03-29) 5 commits
- doc: git-clone: do not autoreference the manpage in itself
- doc: git-clone: apply new documentation formatting guidelines
- doc: git-init: apply new documentation formatting guidelines
- doc: allow literal and emphasis format in doc vs help tests
- doc: rework CodingGuidelines with new formatting rules
@@ -254,7 +251,7 @@ Release tarballs are available at:
literal parts and a few manual pages have been updated as examples.
Will merge to 'next'?
source: <pull.1702.git.1711318739.gitgitgadget@gmail.com>
source: <pull.1702.v2.git.1711711181.gitgitgadget@gmail.com>
* mg/editorconfig-makefile (2024-03-23) 1 commit
@@ -437,7 +434,8 @@ Release tarballs are available at:
source: <cover.1711001016.git.dsimic@manjaro.org>
* jc/apply-parse-diff-git-header-names-fix (2024-03-28) 2 commits
* jc/apply-parse-diff-git-header-names-fix (2024-03-29) 3 commits
- t4126: fix "funny directory name" test on Windows (again)
(merged to 'next' on 2024-03-28 at a35de15836)
+ t4126: make sure a directory with SP at the end is usable
(merged to 'next' on 2024-03-27 at d586367985)
@@ -447,9 +445,10 @@ Release tarballs are available at:
when the change was about an empty file created in or deleted from
a directory whose name ends with a SP, which has been corrected.
Will merge to 'master'.
source: <xmqqh6gqt674.fsf_-_@gitster.g>
Will merge to 'next'?
source: <xmqqfrwlltjn.fsf@gitster.g>
source: <xmqqh6gqt674.fsf_-_@gitster.g>
source: <xmqq5xx50x8p.fsf_-_@gitster.g>
* jk/pretty-subject-cleanup (2024-03-22) 7 commits