Skip to contentSkip to conversation

What's cooking in git.git (Jun 2024, #08; Mon, 24)

DISCUSSION Junio C Hamano 2 participants 3 messages Jun 25, 2024 – Jun 26, 2024

lore
Share & tools
lore
#0 lore raw

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-scm/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']

* jc/add-i-retire-usebuiltin-config (2024-06-05) 1 commit (merged to 'next' on 2024-06-17 at e1fc71db3a)
+ add-i: finally retire add.interactive.useBuiltin

For over a year, setting add.interactive.useBuiltin configuration variable did nothing but giving a "this does not do anything" warning. Finally remove it.
source: <[email protected]>

* jc/no-default-attr-tree-in-bare (2024-06-05) 1 commit (merged to 'next' on 2024-06-17 at 6bfacc9102)
+ attr.tree: HEAD:.gitattributes is no longer the default in a bare repo

Earlier we stopped using the tree of HEAD as the default source of attributes in a bare repository, but failed to document it. This has been corrected.
source: <[email protected]>

* jc/worktree-git-path (2024-06-08) 1 commit (merged to 'next' on 2024-06-17 at a87c318e45)
+ worktree_git_path(): move the declaration to path.h

Code cleanup.
source: <[email protected]>

* kl/attr-read-attr-fromindex-msan-workaround (2024-06-17) 1 commit (merged to 'next' on 2024-06-18 at eebafb2d71)
+ attr: fix msan issue in read_attr_from_index

Code clarification to avoid an appearance of using an uninitialized variable.
source: <[email protected]>

* tb/commit-graph-use-tempfile (2024-06-07) 2 commits (merged to 'next' on 2024-06-17 at e0baebe6b3)
+ server-info.c: remove temporary info files on exit
+ commit-graph.c: remove temporary graph layers on exit

"git update-server-info" and "git commit-graph --write" have been updated to use the tempfile API to avoid leaving cruft after failing.
source: <[email protected]>

* tb/precompose-getcwd (2024-05-31) 1 commit (merged to 'next' on 2024-06-17 at 7596abec9f)
+ 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. This still does not address the case where core.precomposeUnicode configuration is not defined globally.
source: <[email protected]>

* tb/pseudo-merge-reachability-bitmap (2024-06-14) 27 commits
(merged to 'next' on 2024-06-14 at 447d99e1c3)
+ pack-bitmap.c: ensure pseudo-merge offset reads are bounded
+ Documentation/technical/bitmap-format.txt: add missing position table (merged to 'next' on 2024-06-03 at fcaa39de12)
+ t/perf: implement performance 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 --notick 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
+ pseudo-merge: implement support for selecting pseudo-merge commits
+ config: introduce git_config_double()
+ 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()
+ ewah: implement ewah_bitmap_is_subset()
+ Documentation/technical: describe pseudo-merge bitmaps format
+ Documentation/gitpacking.txt: describe pseudo-merge bitmaps
+ Documentation/gitpacking.txt: initial commit
+ Merge branch 'tb/pack-bitmap-write-cleanups' into tb/pseudo-merge-reachability-bitmap

The pseudo-merge reachability bitmap to help more efficient storage of the reachability bitmap in a repository with too many refs has been added.
source: <[email protected]>
source: <[email protected]>

--------------------------------------------------
[New Topics]

* jc/patch-id (2024-06-21) 5 commits
- patch-id: tighten code to detect the patch header
- patch-id: rewrite code that detects the beginning of a patch
- patch-id: make get_one_patchid() more extensible
- patch-id: call flush_current_id() only when needed
- t4204: patch-id supports various input format

The patch parser in "git patch-id" has been tightened to avoid getting confused by lines that look like a patch header in the log message.

Needs review.
source: <[email protected]>

* jc/fuzz-sans-curl (2024-06-21) 1 commit
- fuzz: minimum fuzzers environment lacks libcURL

CI job to build minimum fuzzers learned to pass NO_CURL=NoThanks to the build procedure, as its build environment does not offer, or the rest of the build needs, anything cURL.

Will merge to 'next'.
source: <[email protected]>

* ew/object-convert-leakfix (2024-06-24) 1 commit
- object-file: fix leak on conversion failure

Leakfix.

Will merge to 'next'.
source: <20240622043648.M78681@dcvr>

* rs/diff-color-moved-w-no-ext-diff-fix (2024-06-24) 1 commit
- diff: allow --color-moved with --no-ext-diff

"git diff --no-ext-diff" when diff.external is configured ignored the "--color-moved" option.

Will merge to 'next'.
source: <[email protected]>

--------------------------------------------------
[Cooking]

* kz/merge-fail-early-upon-refresh-failure (2024-06-18) 1 commit (merged to 'next' on 2024-06-20 at 01d4bdd019)
+ merge: avoid write merge state when unable to write index

When "git merge" sees that the index cannot be refreshed (e.g. due to another process doing the same in the background), it died but after writing MERGE_HEAD etc. files, which was useless for the purpose to recover from the failure.

Will merge to 'master'.
source: <[email protected]>

* ds/sparse-lstat-caching (2024-06-20) 5 commits
- sparse-index: improve lstat caching of sparse paths
- sparse-index: count lstat() calls
- sparse-index: use strbuf in path_found()
- sparse-index: refactor path_found()
- sparse-index: refactor skip worktree retry logic

The code to deal with modified paths that are out-of-cone in a sparsely checked out working tree has been optimized.

Needs review.
source: <[email protected]>

* jk/fetch-pack-fsck-wo-lock-pack (2024-06-20) 1 commit (merged to 'next' on 2024-06-20 at c8c41abe07)
+ fetch-pack: fix segfault when fscking without --lock-pack

"git fetch-pack -k -k" without passing "--lock-pack" (which we never do ourselves) did not work at all, which has been corrected.

Will merge to 'master'.
source: <[email protected]>

* jk/t5500-typofix (2024-06-20) 1 commit
(merged to 'next' on 2024-06-20 at cf953645e3)
+ t5500: fix mistaken $SERVER reference in helper function

A helper function shared between two tests had a copy-paste bug, which has been corrected.

Will merge to 'master'.
source: <[email protected]>

* js/mingw-remove-unused-extern-decl (2024-06-20) 1 commit (merged to 'next' on 2024-06-20 at 65b323930f)
+ mingw: drop bogus (and unneeded) declaration of _pgmptr

An unused extern declaration for mingw has been removed to prevent it from causing build failure.

Will merge to 'master'.
source: <[email protected]>

* rb/build-options-w-lib-versions (2024-06-21) 3 commits
- version: teach --build-options to reports zlib version information
- version: teach --build-options to reports libcurl version information (merged to 'next' on 2024-06-20 at b75df251ae)
+ version: --build-options reports OpenSSL version information

"git version --build-options" reports the version information of OpenSSL and other libraries (if used) in the build.

Will merge to 'next' and then to 'master'.
source: <[email protected]>
source: <[email protected]>

* rj/pager-die-upon-exec-failure (2024-06-21) 1 commit
- pager: die when paging to non-existing command

When GIT_PAGER failed to spawn, depending on the code path taken, we failed immediately (correct) or just spew the payload to the standard output (incorrect). The code now always fail immediately when GIT_PAGER fails.

Will merge to 'next'?
source: <[email protected]>

* rs/remove-unused-find-header-mem (2024-06-20) 1 commit (merged to 'next' on 2024-06-20 at 068c785d77)
+ commit: remove find_header_mem()

Code clean-up.

Will merge to 'master'.
source: <[email protected]>

* ew/cat-file-unbuffered-tests (2024-06-20) 2 commits (merged to 'next' on 2024-06-24 at d605297495)
+ t1006: ensure cat-file info isn't buffered by default
+ Git.pm: use array in command_bidi_pipe example

The output from "git cat-file --batch-check" and "--batch-command (info)" should not be unbuffered, for which some tests have been added.

Will merge to 'master'.
source: <[email protected]>
source: <20240618213041.M462972@dcvr>

* cp/unit-test-reftable-tree (2024-06-13) 5 commits
- t-reftable-tree: improve the test for infix_walk()
- t-reftable-tree: add test for non-existent key
- t-reftable-tree: split test_tree() into two sub-test functions
- t: move reftable/tree_test.c to the unit testing framework
- reftable: remove unnecessary curly braces in reftable/tree.c

A test in reftable library has been rewritten using the unit test framework.

Needs review.
source: <[email protected]>

* ps/use-the-repository (2024-06-14) 22 commits
(merged to 'next' on 2024-06-24 at ca97784ba8)
+ hex: guard declarations with USE_THE_REPOSITORY_VARIABLE
+ t/helper: remove dependency on the_repository in "proc-receive"
+ t/helper: fix segfault in "oid-array" command without repository
+ t/helper: use correct object hash in partial-clone helper
+ compat/fsmonitor: fix socket path in networked SHA256 repos
+ replace-object: use hash algorithm from passed-in repository
+ protocol-caps: use hash algorithm from passed-in repository
+ oidset: pass hash algorithm when parsing file
+ http-fetch: don't crash when parsing packfile without a repo
+ hash-ll: merge with "hash.h"
+ refs: avoid include cycle with "repository.h"
+ global: introduce USE_THE_REPOSITORY_VARIABLE macro
+ hash: require hash algorithm in empty_tree_oid_hex()
+ hash: require hash algorithm in is_empty_{blob,tree}_oid()
+ hash: make is_null_oid() independent of the_repository
+ hash: convert oidcmp() and oideq() to compare whole hash
+ global: ensure that object IDs are always padded
+ hash: require hash algorithm in oidread() and oidclr()
+ hash: require hash algorithm in hasheq(), hashcmp() and hashclr()
+ hash: drop (mostly) unused is_empty_{blob,tree}_sha1() functions
+ Merge branch 'gt/unit-test-oidtree' into ps/use-the-repository
+ Merge branch 'ps/ref-storage-migration' into ps/use-the-repository

A CPP macro USE_THE_REPOSITORY_VARIABLE is introduced to help transition the codebase to rely less on the availability of the singleton the_repository instance.

Will merge to 'master'.
source: <[email protected]>

* sj/ref-fsck (2024-06-20) 7 commits
- fsck: add ref content check for files backend
- fsck: add ref name check for files backend
- files-backend: add unified interface for refs scanning
- builtin/fsck: add git-refs verify child process
- builtin/refs: add verify subcommand
- refs: set up ref consistency check infrastructure
- fsck: add refs check interfaces to interact with fsck error levels

"git fsck" infrastructure has been taught to also check the sanity of the ref database, in addition to the object database.

Needs review.
source: <ZnKKy52QFO2UhqM6@ArchLinux>

* en/ort-inner-merge-error-fix (2024-06-20) 7 commits
- merge-ort: convert more error() cases to path_msg()
- merge-ort: upon merge abort, only show messages causing the abort
- merge-ort: loosen commented requirements
- merge-ort: clearer propagation of failure-to-function from merge_submodule
- merge-ort: fix type of local 'clean' var in handle_content_merge ()
- merge-ort: maintain expected invariant for priv member
- merge-ort: extract handling of priv member into reusable function

The "ort" merge backend saw one bugfix for a crash that happens when inner merge gets killed, and assorted code clean-ups.

Needs review.
source: <[email protected]>

* cp/unit-test-reftable-pq (2024-06-14) 7 commits
- t-reftable-pq: add tests for merged_iter_pqueue_top()
- t-reftable-pq: add test for index based comparison
- t-reftable-pq: make merged_iter_pqueue_check() callable by reference
- t-reftable-pq: make merged_iter_pqueue_check() static
- t: move reftable/pq_test.c to the unit testing framework
- reftable: change the type of array indices to 'size_t' in reftable/pq.c
- reftable: remove unncessary curly braces in reftable/pq.c

The tests for "pq" part of reftable library got rewritten to use the unit test framework.

Needs review.
source: <[email protected]>

* jc/archive-prefix-with-add-virtual-file (2024-06-14) 1 commit
- archive: document that --add-virtual-file takes full path

"git archive --add-virtual-file=<path>:<contents>" never paid attention to the --prefix=<prefix> option but the documentation said it would. The documentation has been corrected.

Waiting for comments.
source: <[email protected]>

* jk/remote-wo-url (2024-06-14) 11 commits
- remote: drop checks for zero-url case
- remote: always require at least one url in a remote
- t5801: test remote.*.vcs config
- t5801: make remote-testgit GIT_DIR setup more robust
- remote: allow resetting url list
- config: document remote.*.url/pushurl interaction
- remote: simplify url/pushurl selection
- remote: use strvecs to store remote url/pushurl
- remote: transfer ownership of memory in add_url(), etc
- remote: refactor alias_url() memory ownership
- archive: fix check for missing url

Memory ownership rules for the in-core representation of remote.*.url configuration values have been straightened out, which resulted in a few leak fixes and code clarification.

Waiting for comments.
source: <[email protected]>

* db/date-underflow-fix (2024-06-13) 4 commits
- SQUASH??? skip "near the end-of-git-time" tests on 32-bit systems
- SQUASH??? t0006: simplify prerequisite
- SQUASH??? the git-end-of-time is beyond time_t on 32-bit systems
- date: detect underflow/overflow when parsing dates with timezone offset

date parser updates to be more careful about underflowing epoch based timestamp.

Expecting a reroll.
cf. <[email protected]>
cf. <[email protected]>
source: <[email protected]>

* tb/incremental-midx-part-1 (2024-06-07) 19 commits
- midx: implement support for writing incremental MIDX chains
- t/t5313-pack-bounds-checks.sh: prepare for sub-directories
- t: retire 'GIT_TEST_MULTI_PACK_INDEX_WRITE_BITMAP'
- midx: implement verification support for incremental MIDXs
- midx: support reading incremental MIDX chains
- midx: teach midx_fanout_add_midx_fanout() about incremental MIDXs
- midx: teach midx_preferred_pack() about incremental MIDXs
- midx: teach midx_contains_pack() about incremental MIDXs
- midx: remove unused midx_locate_pack()
- midx: teach fill_midx_entry() about incremental MIDXs
- midx: teach nth_midxed_offset() about incremental MIDXs
- midx: teach bsearch_midx() about incremental MIDXs
- midx: introduce bsearch_one_midx()
- midx: teach nth_bitmapped_pack() about incremental MIDXs
- midx: teach nth_midxed_object_oid() about incremental MIDXs
- midx: teach prepare_midx_pack() about incremental MIDXs
- midx: teach nth_midxed_pack_int_id() about incremental MIDXs
- midx: add new fields for incremental MIDX chains
- Documentation: describe incremental MIDX format

Incremental updates of multi-pack index files.

Needs review.
source: <[email protected]>

* vd/mktree (2024-06-20) 17 commits
- mktree: remove entries when mode is 0
- mktree: allow deeper paths in input
- mktree: optionally add to an existing tree
- mktree: add directory-file conflict hashmap
- mktree: use iterator struct to add tree entries to index
- mktree: create tree using an in-core index
- mktree: overwrite duplicate entries
- mktree: validate paths more carefully
- mktree: add a --literally option
- mktree.c: do not fail on mismatched submodule type
- mktree: use read_index_info to read stdin lines
- index-info.c: parse object type in provided in read_index_info
- index-info.c: return unrecognized lines to caller
- update-index: generalize 'read_index_info'
- mktree: use non-static tree_entry array
- mktree: rename treeent to tree_entry
- mktree: use OPT_BOOL

"git mktree" has been rewritten, taking advantage of the cache-tree API.

Needs review.
source: <[email protected]>

* xx/bundie-uri-fixes (2024-06-20) 3 commits
- unbundle: extend object verification for fetches
- fetch-pack: expose fsckObjects configuration logic
- bundle-uri: verify oid before writing refs

When bundleURI interface fetches multiple bundles, Git failed to take full advantage of all bundles and ended up slurping duplicated objects.

Will merge to 'next'?
source: <[email protected]>

* ps/leakfixes-more (2024-06-11) 30 commits
- builtin/blame: fix leaking ignore revs files
- builtin/blame: fix leaking prefixed paths
- blame: fix leaking data for blame scoreboards
- line-range: plug leaking find functions
- merge: fix leaking merge bases
- builtin/merge: fix leaking struct cmdnames in get_strategy()
- sequencer: fix memory leaks in make_script_with_merges()
- builtin/clone: plug leaking HEAD ref in wanted_peer_refs()
- apply: fix leaking string in match_fragment()
- sequencer: fix leaking string buffer in commit_staged_changes()
- commit: fix leaking parents when calling commit_tree_extended()
- config: fix leaking "core.notesref" variable
- rerere: fix various trivial leaks
- builtin/stash: fix leak in show_stash()
- revision: free diff options
- builtin/log: fix leaking commit list in git-cherry(1)
- merge-recursive: fix memory leak when finalizing merge
- builtin/merge-recursive: fix leaking object ID bases
- builtin/difftool: plug memory leaks in run_dir_diff()
- object-name: free leaking object contexts
- builtin/rev-list: fix leaking bitmap index when calculating disk usage
- notes: fix memory leak when pruning notes
- revision: fix leaking display notes
- merge-recursive: fix leaking rename conflict info
- biultin/rev-parse: fix memory leaks in --parseopt mode
- bundle: plug leaks in create_bundle()
- notes-utils: free note trees when releasing copied notes
- parse-options: fix leaks for users of OPT_FILENAME
- revision: fix memory leak when reversing revisions
- Merge branch 'ps/leakfixes' into ps/leakfixes-more

More memory leaks have been plugged.

Needs review.
source: <[email protected]>

* pp/add-parse-range-unit-test (2024-05-27) 1 commit
- apply: add unit tests for parse_range

A unit test for code that parses the hunk offset and length from a patch fragment header as been added.

Expecting a reroll.
cf. <[email protected]>
source: <[email protected]>

* ie/config-includeif-hostname (2024-03-19) 2 commits
- config: learn the "hostname:" includeIf condition
- t: add a test helper for getting hostname

The conditional inclusion mechanism for configuration files learned to switch on the hostname.

Expecting a reroll.
cf. <[email protected]> cf. <[email protected]>
source: <[email protected]>

* cw/git-std-lib (2024-02-28) 4 commits
. SQUASH??? get rid of apparent debugging crufts . test-stdlib: show that git-std-lib is independent . git-std-lib: introduce Git Standard Library . pager: include stdint.h because uintmax_t is used

Split libgit.a out to a separate git-std-lib tor easier reuse.

Expecting a reroll.
source: <[email protected]>

* bk/complete-dirname-for-am-and-format-patch (2024-01-12) 1 commit
- completion: dir-type optargs for am, format-patch

Command line completion support (in contrib/) has been updated for a few commands to complete directory names where a directory name is expected.

Expecting a reroll.
cf. <[email protected]>
cf. <[email protected]>
source: <[email protected]>

* bk/complete-send-email (2024-01-12) 1 commit
- completion: don't complete revs when --no-format-patch

Command line completion support (in contrib/) has been taught to avoid offering revision names as candidates to "git send-email" when the command is used to send pre-generated files.

Expecting a reroll.
cf. <CAC4O8c88Z3ZqxH2VVaNPpEGB3moL5dJcg3cOWuLWwQ_hLrJMtA@mail.gmail.com>
source: <[email protected]>

* tb/path-filter-fix (2024-01-31) 16 commits
- bloom: introduce deinit_bloom_filters()
- commit-graph: reuse existing Bloom filters where possible
- object.h: fix mis-aligned flag bits table
- commit-graph: new Bloom filter version that fixes murmur3
- commit-graph: unconditionally load Bloom filters
- bloom: prepare to discard incompatible Bloom filters
- bloom: annotate filters with hash version
- repo-settings: introduce commitgraph.changedPathsVersion
- t4216: test changed path filters with high bit paths
- t/helper/test-read-graph: implement bloom-filters mode
- bloom.h: make load_bloom_filter_from_graph() public
- t/helper/test-read-graph.c: extract dump_graph_info()
- gitformat-commit-graph: describe version 2 of BDAT
- commit-graph: ensure Bloom filters are read with consistent settings
- revision.c: consult Bloom filters for root commits
- t/t4216-log-bloom.sh: harden test_bloom_filters_not_used()

The Bloom filter used for path limited history traversal was broken on systems whose "char" is unsigned; update the implementation and bump the format version to 2.

Waiting for a final ack?
cf. <[email protected]>
source: <[email protected]>

* jc/rerere-cleanup (2023-08-25) 4 commits
- rerere: modernize use of empty strbuf
- rerere: try_merge() should use LL_MERGE_ERROR when it means an error
- rerere: fix comment on handle_file() helper
- rerere: simplify check_one_conflict() helper function

Code clean-up.

Not ready to be reviewed yet.
source: <[email protected]>

--------------------------------------------------
[Discarded]

* rj/add-p-pager (2024-06-04) 6 commits
. add-patch: introduce the command '|'
. test-terminal: introduce --no-stdin-pty
. pager: introduce setup_custom_pager
. pager: introduce wait_for_pager
. pager: do not close fd 2 unnecessarily
. add-patch: test for 'p' command

"git add -i" and friends learned a new '|' command that sends the current hunk to the pager, instead of dumping it to the terminal.

Expecting a reroll to work well with jk/am-retry
source: <[email protected]>

#1 lore raw
Quoted 10 lines · Junio C Hamano

* rj/pager-die-upon-exec-failure (2024-06-21) 1 commit
- pager: die when paging to non-existing command

When GIT_PAGER failed to spawn, depending on the code path taken, we failed immediately (correct) or just spew the payload to the standard output (incorrect). The code now always fail immediately when GIT_PAGER fails.

Will merge to 'next'?
source: <[email protected]>

The version queued is:
<[email protected]>

Hannes pointed out a minor bug that's worth fixing. I sent an update:

https://lore.kernel.org/git/[email protected]

Other than that, based on the comments received, I think it is ready to be merged.

Thanks.

#2 lore raw
In reply to Junio C Hamano
Quoted 6 lines · Junio C Hamano

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.

We seem to have too many topics in flight that haven't received adequate reviews. Can contributors divert effort to come up with new patches and topics to reviewing patches already in flight?

Here is a summary of topics that are still marked as "Needs review" in the draft of the next issue of "What's cooking report".

Needs review.
- tb/incremental-midx-part-1 06-07 #19
source: <[email protected]>
- cp/unit-test-reftable-tree 06-13 #5
source: <[email protected]>
- cp/unit-test-reftable-pq 06-14 #7
source: <[email protected]>
- vd/mktree 06-20 #17
source: <[email protected]>
- en/ort-inner-merge-error-fix 06-20 #7
source: <[email protected]>
- jc/patch-id 06-21 #5
source: <[email protected]>

There are a few topics that are marked as "Expecting a reroll", but I do not expect they will see an immediate action from their authors if I repeated them here, so I won't do that X-<. Instead, I'll mark the older ones among them as "Will discard".

Thanks.