To: git@vger.kernel.org
Bcc: lwn@lwn.net
-Subject: What's cooking in git.git (Jul 2020, #04; Wed, 22)
-X-master-at: b066807397fd55553f4910ede74839e319b661fd
-X-next-at: 839af2c2686bba67b3e8cea649583ed99b2326e6
+Subject: What's cooking in git.git (Jul 2020, #05; Mon, 27)
+X-master-at: 47ae905ffb98cc4d4fd90083da6bc8dab55d9ecc
+X-next-at: 6104cc2f0b60537336b3f2ee6fc82132e2b84cd3
-What's cooking in git.git (Jul 2020, #04; Wed, 22)
+What's cooking in git.git (Jul 2020, #05; Mon, 27)
--------------------------------------------------
Here are the topics that have been cooking. Commits prefixed with '-' are
with '+' are in 'next'. The ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
-I just tagged Git 2.28-rc2; we should be pretty in a good shape and
-hopefully the only difference between this and the final would just
-be the translation.
+Git 2.28 has been tagged. We'll go slow for a few days to gauge the
+initial reaction to it and see if there is no major brown-paper-bag
+issues discovered. Following that, majority of topics that have
+been cooking in 'next' will be merged to 'master', the tip of 'next'
+will be rewound and rebuilt on top of the updated 'master', near the
+end of this week. The 'next' branch then will start taking new
+topics after that.
+
+During the next cycle for 2.29, we will decide the direction of
+follow-up work, if any is needed, for the init.defaultBranch topic
+we did the last cycle.
You can find the changes described here in the integration branches of the
repositories listed at
http://git-blame.blogspot.com/p/git-public-repositories.html
--------------------------------------------------
-[Graduated to 'master']
+[New Topics]
+
+* jb/doc-packfile-name (2020-07-22) 1 commit
+ - pack-write/docs: update regarding pack naming
-* dl/branch-cleanup (2020-07-18) 1 commit
- (merged to 'next' on 2020-07-18 at 942efa1f99)
- + t3200: don't grep for `strerror()` string
+ Doc update.
+
+ Will merge to 'next'.
- Last minute fix-up to tests for portability.
+* dd/send-email-config (2020-07-23) 1 commit
+ - git-send-email: die if sendmail.* config is set
-* en/sparse-status (2020-07-20) 1 commit
- (merged to 'next' on 2020-07-20 at 6aa5c12b74)
- + git-prompt: change == to = for zsh's sake
+ Stop when "sendmail.*" configuration variables are defined, which
+ could be a mistaken attempt to define "sendemail.*" variables.
- Fix to a "git prompt" regression during this development cycle.
+--------------------------------------------------
+[Stalled]
+* jx/proc-receive-hook (2020-05-18) 11 commits
+ - doc: add documentation for the proc-receive hook
+ - transport: parse report options for tracking refs
+ - t5411: test updates of remote-tracking branches
+ - receive-pack: new config receive.procReceiveRefs
+ - refs.c: refactor to reuse ref_is_hidden()
+ - receive-pack: feed report options to post-receive
+ - doc: add document for capability report-status-v2
+ - New capability "report-status-v2" for git-push
+ - receive-pack: add new proc-receive hook
+ - t5411: add basic test cases for proc-receive hook
+ - transport: not report a non-head push as a branch
-* jc/relnotes-v0-extension-update (2020-07-17) 1 commit
- (merged to 'next' on 2020-07-18 at 4e03396489)
- + RelNotes: update the v0 with extension situation
+ "git receive-pack" that accepts requests by "git push" learned to
+ outsource most of the ref updates to the new "proc-receive" hook.
- Last minute fix-up to the release notes.
+ Needs review.
-* jn/v0-with-extensions-fix (2020-07-16) 2 commits
- + repository: allow repository format upgrade with extensions
- + Revert "check_repository_format_gently(): refuse extensions for old repositories"
- (this branch is used by jk/reject-newer-extensions-in-v0.)
+* mf/submodule-summary-with-correct-repository (2020-06-24) 2 commits
+ - submodule: use submodule repository when preparing summary
+ - revision: use repository from rev_info when parsing commits
- In 2.28-rc0, we corrected a bug that some repository extensions are
- honored by mistake even in a version 0 repositories (these
- configuration variables in extensions.* namespace were supposed to
- have special meaning in repositories whose version numbers are 1 or
- higher), but this was a bit too big a change.
+ "git diff/show" on a change that involves a submodule used to read
+ the information on commits in the submodule from a wrong repository
+ and gave a wrong information when the commit-graph is involved.
+ Needs tests.
-* js/pu-to-seen (2020-07-18) 1 commit
- (merged to 'next' on 2020-07-18 at bb6ee9441b)
- + gitworkflows.txt: fix broken subsection underline
- Last minute fix-up to documentation.
+* dr/push-remoteref-fix (2020-04-23) 1 commit
+ - remote.c: fix handling of %(push:remoteref)
+
+ The "%(push:remoteref)" placeholder in the "--format=" argument of
+ "git format-patch" (and friends) only showed what got explicitly
+ configured, not what ref at the receiving end would be updated when
+ "git push" was used, as it ignored the default behaviour (e.g. update
+ the same ref as the source).
+
+ Expecting a reroll.
+ cf. <20200416152145.wp2zeibxmuyas6y6@feanor>
+
+
+* mr/bisect-in-c-2 (2020-07-17) 14 commits
+ - SQUASH??? do not add new users of git_path_bisect_head()
+ - bisect--helper: retire `--bisect-autostart` subcommand
+ - bisect--helper: retire `--write-terms` subcommand
+ - bisect--helper: retire `--check-expected-revs` subcommand
+ - bisect--helper: reimplement `bisect_state` & `bisect_head` shell functions in C
+ - bisect--helper: retire `--next-all` subcommand
+ - bisect--helper: retire `--bisect-clean-state` subcommand
+ - bisect--helper: finish porting `bisect_start()` to C
+ - bisect--helper: reimplement `bisect_next` and `bisect_auto_next` shell functions in C
+ - bisect: call 'clear_commit_marks_all()' in 'bisect_next_all()'
+ - bisect--helper: reimplement `bisect_autostart` shell function in C
+ - bisect--helper: introduce new `write_in_file()` function
+ - bisect--helper: use '-res' in 'cmd_bisect__helper' return
+ - bisect--helper: BUG() in cmd_*() on invalid subcommand
+
+ Rewrite of the remainder of "git bisect" script in C continues.
+
+ Needs more work.
+
+
+* mk/use-size-t-in-zlib (2018-10-15) 1 commit
+ - zlib.c: use size_t for size
+
+ The wrapper to call into zlib followed our long tradition to use
+ "unsigned long" for sizes of regions in memory, which have been
+ updated to use "size_t".
--------------------------------------------------
-[New Topics]
+[Cooking]
* jk/reject-newer-extensions-in-v0 (2020-07-16) 1 commit
(merged to 'next' on 2020-07-16 at 85f634d5a6)
Will merge to 'next'.
-* sg/ci-git-path-fix-with-pyenv (2020-07-21) 1 commit
- - travis-ci: remove bogus 'pyenv' in the Linux jobs
+* sg/ci-git-path-fix-with-pyenv (2020-07-23) 1 commit
+ - ci: use absolute PYTHON_PATH in the Linux jobs
CI fixup---tests of Python scripts didn't use the version of Git
that is being tested.
Will merge to 'next'.
---------------------------------------------------
-[Stalled]
-* jx/proc-receive-hook (2020-05-18) 11 commits
- - doc: add documentation for the proc-receive hook
- - transport: parse report options for tracking refs
- - t5411: test updates of remote-tracking branches
- - receive-pack: new config receive.procReceiveRefs
- - refs.c: refactor to reuse ref_is_hidden()
- - receive-pack: feed report options to post-receive
- - doc: add document for capability report-status-v2
- - New capability "report-status-v2" for git-push
- - receive-pack: add new proc-receive hook
- - t5411: add basic test cases for proc-receive hook
- - transport: not report a non-head push as a branch
-
- "git receive-pack" that accepts requests by "git push" learned to
- outsource most of the ref updates to the new "proc-receive" hook.
-
- Needs review.
-
-
-* mf/submodule-summary-with-correct-repository (2020-06-24) 2 commits
- - submodule: use submodule repository when preparing summary
- - revision: use repository from rev_info when parsing commits
-
- "git diff/show" on a change that involves a submodule used to read
- the information on commits in the submodule from a wrong repository
- and gave a wrong information when the commit-graph is involved.
-
- Needs tests.
-
-
-* dr/push-remoteref-fix (2020-04-23) 1 commit
- - remote.c: fix handling of %(push:remoteref)
-
- The "%(push:remoteref)" placeholder in the "--format=" argument of
- "git format-patch" (and friends) only showed what got explicitly
- configured, not what ref at the receiving end would be updated when
- "git push" was used, as it ignored the default behaviour (e.g. update
- the same ref as the source).
-
- Expecting a reroll.
- cf. <20200416152145.wp2zeibxmuyas6y6@feanor>
-
-
-* mr/bisect-in-c-2 (2020-07-17) 14 commits
- - SQUASH??? do not add new users of git_path_bisect_head()
- - bisect--helper: retire `--bisect-autostart` subcommand
- - bisect--helper: retire `--write-terms` subcommand
- - bisect--helper: retire `--check-expected-revs` subcommand
- - bisect--helper: reimplement `bisect_state` & `bisect_head` shell functions in C
- - bisect--helper: retire `--next-all` subcommand
- - bisect--helper: retire `--bisect-clean-state` subcommand
- - bisect--helper: finish porting `bisect_start()` to C
- - bisect--helper: reimplement `bisect_next` and `bisect_auto_next` shell functions in C
- - bisect: call 'clear_commit_marks_all()' in 'bisect_next_all()'
- - bisect--helper: reimplement `bisect_autostart` shell function in C
- - bisect--helper: introduce new `write_in_file()` function
- - bisect--helper: use '-res' in 'cmd_bisect__helper' return
- - bisect--helper: BUG() in cmd_*() on invalid subcommand
-
- Rewrite of the remainder of "git bisect" script in C continues.
-
- Needs more work.
-
-
-* mk/use-size-t-in-zlib (2018-10-15) 1 commit
- - zlib.c: use size_t for size
-
- The wrapper to call into zlib followed our long tradition to use
- "unsigned long" for sizes of regions in memory, which have been
- updated to use "size_t".
-
---------------------------------------------------
-[Cooking]
-
-* bc/sha-256-part-3 (2020-07-15) 39 commits
+* bc/sha-256-part-3 (2020-07-22) 39 commits
- t: remove test_oid_init in tests
- docs: add documentation for extensions.objectFormat
- ci: run tests with SHA-256
"git fetch" learned the "--[no-]write-fetch-head" option to
optionally stop describing what was fetched in FETCH_HEAD.
- Will merge to 'next' after the release.
+ Needs more work.
* mp/complete-show-color-moved (2020-07-15) 1 commit
Command line completion (in contrib/) update.
- Will merge to 'next' after the release.
+ Will merge to 'next'.
A follow-up patch to reduce duplication may be warranted.
* hn/reftable-prep-part-2 (2020-07-16) 3 commits
- . Make HEAD a PSEUDOREF rather than PER_WORKTREE.
- . Modify pseudo refs through ref backend storage
- . t1400: use git rev-parse for testing PSEUDOREF existence
+ - Make HEAD a PSEUDOREF rather than PER_WORKTREE.
+ - Modify pseudo refs through ref backend storage
+ - t1400: use git rev-parse for testing PSEUDOREF existence
(this branch uses hn/reftable.)
Further preliminary change to refs API.
Will cook in 'next'.
-* ds/maintenance (2020-07-07) 21 commits
+* ds/maintenance (2020-07-23) 18 commits
+ - maintenance: add trace2 regions for task execution
- midx: use start_delayed_progress()
- - maintenance: add pack-files auto condition
+ - maintenance: add incremental-repack auto condition
- maintenance: create auto condition for loose-objects
- maintenance: add auto condition for commit-graph task
- maintenance: use pointers to check --auto
- maintenance: create maintenance.<task>.enabled config
- - maintenance: auto-size pack-files batch
- - maintenance: add pack-files task
+ - maintenance: auto-size incremental-repack batch
+ - maintenance: add incremental-repack task
- maintenance: add loose-objects task
- - maintenance: add fetch task
+ - maintenance: add prefetch task
- maintenance: take a lock on the objects directory
- maintenance: add --task option
- maintenance: add commit-graph task
- - maintenance: initialize task array and hashmap
+ - maintenance: initialize task array
- maintenance: replace run_auto_gc()
- maintenance: add --quiet option
- maintenance: create basic maintenance runner
- - gc: drop the_repository in log location
- - gc: use repo config
- - gc: use repository in too_many_loose_objects()
- - gc: use the_repository less often
A "git gc"'s big brother has been introduced to take care of more
repository maintenance tasks, not limited to the object database
Will cook in 'next'.
-* tb/upload-pack-filters (2020-07-06) 4 commits
- . upload-pack.c: introduce 'uploadpack.filter.tree.maxDepth'
- . upload-pack.c: pass 'struct list_objects_filter_options *'
- . upload-pack.c: allow banning certain object filter(s)
- . list_objects_filter_options: introduce 'list_object_filter_config_name'
+* tb/upload-pack-filters (2020-07-22) 4 commits
+ - upload-pack.c: introduce 'uploadpackfilter.tree.maxDepth'
+ - upload-pack.c: pass 'struct list_objects_filter_options *'
+ - upload-pack.c: allow banning certain object filter(s)
+ - list_objects_filter_options: introduce 'list_object_filter_config_name'
The component to respond to "git fetch" request is made more
configurable to selectively allow or reject object filtering
specification used for partial cloning.
- Expecting a reroll.
- cf. <20200721202740.GA34538@syl.lan>
-
* mt/hash-to-hex-thread-safety (2020-06-26) 2 commits
- hex: make hash_to_hex_algop() and friends thread-safe
CMake support to build with MSVC for Windows bypassing the Makefile.
- Will merge to 'next' after the release.
+ Will merge to 'next'.
cf. https://github.com/git/git/runs/892824895
projects / thirdparty / git.git / commitdiff
