Re: [ANNOUNCE] Git v2.29.0
Hi, On Mon, Oct 19, 2020 at 11:15 AM Junio C Hamano wrote: > > The latest feature release Git v2.29.0 is now available at the > usual places. It is comprised of 627 non-merge commits since > v2.28.0, contributed by 89 people, 24 of which are new faces. The latest release of git-filter-repo, v2.29.0, is also now available. It is comprised of 7 non-merge commits since v2.28.0, including two changes from new contributors and one change from a previous contributor (besides myself). The public repo of filter-repo is at https://github.com/newren/git-filter-repo The tarballs can be found at: https://github.com/newren/git-filter-repo/releases git-filter-repo can also be installed via a variety of package managers across Windows, Mac OS, or Linux (and maybe others)[1]. New contributors whose contributions weren't in v2.28.0 are as follows. Welcome to the git-filter-repo development community! * Martin Wilck * Tom Matthews Returning contributors who helped this release are as follows. Thanks for your continued support. * Marius Renner [1] https://github.com/newren/git-filter-repo/blob/master/INSTALL.md git-filter-repo 2.29 Release Notes == (Note: Additional information is available for many release notes at https://github.com/newren/git-filter-repo/issues/) * Fixes: * correctly prune nested tags not matching filtering criteria (#134) * only set author from committer if author email not set (#154) * fix typo in docs about converting from bfg-repo-cleaner (#148, #151) * fix NameError in filter-lamely script (#161) * Documentation: * corrected notes about --replace-text regexes (#145) * improved installation instructions, especially for Windows users (#124,#163) Changes since v2.28.0 are as follows: Elijah Newren (4): filter-repo (README): remove outdated 2.28.0-not-yet-released comment filter-repo: correctly prune nested tags not matching filtering criteria git-filter-repo.txt: regexes & globs apply to entire file, not to lines INSTALL.md: add notes about common installation issues Marius Renner (1): filter-lamely: fix NameError because of forgotten fr module prefix Martin Wilck (1): filter-repo: only set author from committer if author email not set Tom Matthews (1): converting-from-bfg-repo-cleaner.md: fix typo
[ANNOUNCE] Git v2.29.0
The latest feature release Git v2.29.0 is now available at the usual places. It is comprised of 627 non-merge commits since v2.28.0, contributed by 89 people, 24 of which are new faces. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/ The following public repositories all have a copy of the 'v2.29.0' tag and the 'master' branch that the tag points at: url = https://kernel.googlesource.com/pub/scm/git/git url = git://repo.or.cz/alt-git.git url = https://github.com/gitster/git New contributors whose contributions weren't in v2.28.0 are as follows. Welcome to the Git development community! Aaron Lipman, Adrian Moennich, Ákos Uzonyi, Antti Keränen, Christian Schlack, Conor Davis, Daniel Santos, Eric Huber, Evan Gates, Han Xin, Hugo Locurcio, Kyohei Kadota, Lin Sun, Nikita Leonov, Noam Yorav-Raphael, pudinha, Raymond E. Pasco, Ryan Zoeller, Samanta Navarro, Serg Tereshchenko, Sibi Siddharthan, Simon Legner, Steve Kemp, and Theodore Dubois. Returning contributors who helped this release are as follows. Thanks for your continued support. Ævar Arnfjörð Bjarmason, Alban Gruin, Alessandro Menti, Alexander Shopov, Alex Henrie, Alex Riesen, Andrei Rybak, Beat Bolli, Ben Wijen, brian m. carlson, Christian Couder, Chris Torek, Danny Lin, Denton Liu, Derrick Stolee, Đoàn Trần Công Danh, Drew DeVault, Edmundo Carmona Antoranz, Elijah Newren, Emily Shaffer, Emir Sarı, Eric Sunshine, Han-Wen Nienhuys, Hariom Verma, Jacob Keller, Jean-Noël Avila, Jeff Hostetler, Jeff King, Jiang Xin, Johannes Berg, Johannes Schindelin, Johannes Sixt, Jonathan Tan, Jordi Mas, Junio C Hamano, Kazuhiro Kato, Luke Diamand, Martin Ågren, Matheus Tavares, Matthew Rogers, Matthias Rüster, Michael Forney, Michal Privoznik, Miriam Rubio, Orgad Shaneh, Patrick Steinhardt, Paul Mackerras, Peter Krefting, Philippe Blain, Phillip Wood, Pranit Bauva, Prathamesh Chavan, Pratyush Yadav, René Scharfe, Rohit Ashiwal, Sergey Organov, Shourya Shukla, Stefan Dotterweich, Stefan Haller, SZEDER Gábor, Taylor Blau, Thomas Guyot-Sionnest, Trần Ngọc Quân, Yi-Jyun Pan, and Роман Донченко. Git 2.29 Release Notes == Updates since v2.28 --- UI, Workflows & Features * "git help log" has been enhanced by sharing more material from the documentation for the underlying "git rev-list" command. * "git for-each-ref --format=<>" learned %(contents:size). * "git merge" learned to selectively omit " into " at the end of the title of default merge message with merge.suppressDest configuration. * The component to respond to "git fetch" request is made more configurable to selectively allow or reject object filtering specification used for partial cloning. * Stop when "sendmail.*" configuration variables are defined, which could be a mistaken attempt to define "sendemail.*" variables. * The existing backends for "git mergetool" based on variants of vim have been refactored and then support for "nvim" has been added. * "git bisect" learns the "--first-parent" option to find the first breakage along the first-parent chain. * "git log --first-parent -p" showed patches only for single-parent commits on the first-parent chain; the "--first-parent" option has been made to imply "-m". Use "--no-diff-merges" to restore the previous behaviour to omit patches for merge commits. * The commit labels used to explain each side of conflicted hunks placed by the sequencer machinery have been made more readable by humans. * The "--batch-size" option of "git multi-pack-index repack" command is now used to specify that very small packfiles are collected into one until the total size roughly exceeds it. * The recent addition of SHA-256 support is marked as experimental in the documentation. * "git fetch" learned --no-write-fetch-head option to avoid writing the FETCH_HEAD file. * Command line completion (in contrib/) usually omits redundant, deprecated and/or dangerous options from its output; it learned to optionally include all of them. * The output from the "diff" family of the commands had abbreviated object names of blobs involved in the patch, but its length was not affected by the --abbrev option. Now it is. * "git worktree" gained a "repair" subcommand to help users recover after moving the worktrees or repository manually without telling Git. Also, "git init --separate-git-dir" no longer corrupts administrative data related to linked worktrees. * The "--format=" option to the "for-each-ref" command and friends learned a few more tricks, e.g. the ":short" suffix that applies to "objectname" now also can be used for "parent", "tree", etc. * "git worktree add" learns that the "-d" is a synonym to "--detach" option to create a new worktree without being on a branch. * "format-patch
RE: [ANNOUNCE] Git v2.29.0-rc2
Junio C Hamano wrote: > An early preview release Git v2.29.0-rc2 is now available for testing ... The release tested 100% clean on NonStop! Regards and thanks, Randall
[ANNOUNCE] Git v2.29.0-rc2
A release candidate Git v2.29.0-rc2 is now available for testing at the usual places. The tree has no change since v2.29.0-rc1 The tarballs are found at: https://www.kernel.org/pub/software/scm/git/testing/ The following public repositories all have a copy of the 'v2.29.0-rc2' tag and the 'master' branch that the tag points at: url = https://kernel.googlesource.com/pub/scm/git/git url = git://repo.or.cz/alt-git.git url = https://github.com/gitster/git Thanks. Git 2.29 Release Notes (draft) == Updates since v2.28 --- UI, Workflows & Features * "git help log" has been enhanced by sharing more material from the documentation for the underlying "git rev-list" command. * "git for-each-ref --format=<>" learned %(contents:size). * "git merge" learned to selectively omit " into " at the end of the title of default merge message with merge.suppressDest configuration. * The component to respond to "git fetch" request is made more configurable to selectively allow or reject object filtering specification used for partial cloning. * Stop when "sendmail.*" configuration variables are defined, which could be a mistaken attempt to define "sendemail.*" variables. * The existing backends for "git mergetool" based on variants of vim have been refactored and then support for "nvim" has been added. * "git bisect" learns the "--first-parent" option to find the first breakage along the first-parent chain. * "git log --first-parent -p" showed patches only for single-parent commits on the first-parent chain; the "--first-parent" option has been made to imply "-m". Use "--no-diff-merges" to restore the previous behaviour to omit patches for merge commits. * The commit labels used to explain each side of conflicted hunks placed by the sequencer machinery have been made more readable by humans. * The "--batch-size" option of "git multi-pack-index repack" command is now used to specify that very small packfiles are collected into one until the total size roughly exceeds it. * The recent addition of SHA-256 support is marked as experimental in the documentation. * "git fetch" learned --no-write-fetch-head option to avoid writing the FETCH_HEAD file. * Command line completion (in contrib/) usually omits redundant, deprecated and/or dangerous options from its output; it learned to optionally include all of them. * The output from the "diff" family of the commands had abbreviated object names of blobs involved in the patch, but its length was not affected by the --abbrev option. Now it is. * "git worktree" gained a "repair" subcommand to help users recover after moving the worktrees or repository manually without telling Git. Also, "git init --separate-git-dir" no longer corrupts administrative data related to linked worktrees. * The "--format=" option to the "for-each-ref" command and friends learned a few more tricks, e.g. the ":short" suffix that applies to "objectname" now also can be used for "parent", "tree", etc. * "git worktree add" learns that the "-d" is a synonym to "--detach" option to create a new worktree without being on a branch. * "format-patch --range-diff= ..HEAD" has been taught not to ignore when is a single version. * "add -p" now allows editing paths that were only added in intent. * The 'meld' backend of the "git mergetool" learned to give the underlying 'meld' the '--auto-merge' option, which would help reduce the amount of text that requires manual merging. * "git for-each-ref" and friends that list refs used to allow only one --merged or --no-merged to filter them; they learned to take combination of both kind of filtering. * "git maintenance", a "git gc"'s big brother, has been introduced to take care of more repository maintenance tasks, not limited to the object database cleaning. * "git receive-pack" that accepts requests by "git push" learned to outsource most of the ref updates to the new "proc-receive" hook. * "git push" that wants to be atomic and wants to send push certificate learned not to prepare and sign the push certificate when it fails the local check (hence due to atomicity it is known that no certificate is needed). * "git commit-graph write" learned to limit the number of bloom filters that are computed from scratch with the --max-new-filters option. * The transport protocol v2 has become the default again. * The installation procedure learned to optionally omit "git-foo" executable files for each 'foo' built-in subcommand, which are only required by old timers that still rely on the age old promise that prepending "git --exec-path" output to PATH early in their script will keep the "git-foo" calls they wrote working. * The command line completion (in contrib/) learned that
[ANNOUNCE] Git v2.29.0-rc1
A release candidate Git v2.29.0-rc1 is now available for testing at the usual places. It is comprised of 605 non-merge commits since v2.28.0, contributed by 77 people, 22 of which are new faces. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/testing/ The following public repositories all have a copy of the 'v2.29.0-rc1' tag and the 'master' branch that the tag points at: url = https://kernel.googlesource.com/pub/scm/git/git url = git://repo.or.cz/alt-git.git url = https://github.com/gitster/git New contributors whose contributions weren't in v2.28.0 are as follows. Welcome to the Git development community! Aaron Lipman, Adrian Moennich, Ákos Uzonyi, Antti Keränen, Christian Schlack, Conor Davis, Eric Huber, Evan Gates, Han Xin, Hugo Locurcio, Kyohei Kadota, Lin Sun, Nikita Leonov, Noam Yorav-Raphael, pudinha, Raymond E. Pasco, Ryan Zoeller, Samanta Navarro, Sibi Siddharthan, Simon Legner, Steve Kemp, and Theodore Dubois. Returning contributors who helped this release are as follows. Thanks for your continued support. Ævar Arnfjörð Bjarmason, Alban Gruin, Alex Henrie, Alex Riesen, Andrei Rybak, Beat Bolli, Ben Wijen, brian m. carlson, Christian Couder, Chris Torek, Danny Lin, Denton Liu, Derrick Stolee, Đoàn Trần Công Danh, Drew DeVault, Edmundo Carmona Antoranz, Elijah Newren, Emily Shaffer, Eric Sunshine, Han-Wen Nienhuys, Hariom Verma, Jacob Keller, Jean-Noël Avila, Jeff Hostetler, Jeff King, Jiang Xin, Johannes Berg, Johannes Schindelin, Johannes Sixt, Jonathan Tan, Junio C Hamano, Kazuhiro Kato, Luke Diamand, Martin Ågren, Matheus Tavares, Matthew Rogers, Michael Forney, Michal Privoznik, Miriam Rubio, Orgad Shaneh, Patrick Steinhardt, Paul Mackerras, Philippe Blain, Phillip Wood, Pranit Bauva, Prathamesh Chavan, René Scharfe, Rohit Ashiwal, Sergey Organov, Shourya Shukla, Stefan Dotterweich, SZEDER Gábor, Taylor Blau, Thomas Guyot-Sionnest, and Роман Донченко. Git 2.29 Release Notes (draft) == Updates since v2.28 --- UI, Workflows & Features * "git help log" has been enhanced by sharing more material from the documentation for the underlying "git rev-list" command. * "git for-each-ref --format=<>" learned %(contents:size). * "git merge" learned to selectively omit " into " at the end of the title of default merge message with merge.suppressDest configuration. * The component to respond to "git fetch" request is made more configurable to selectively allow or reject object filtering specification used for partial cloning. * Stop when "sendmail.*" configuration variables are defined, which could be a mistaken attempt to define "sendemail.*" variables. * The existing backends for "git mergetool" based on variants of vim have been refactored and then support for "nvim" has been added. * "git bisect" learns the "--first-parent" option to find the first breakage along the first-parent chain. * "git log --first-parent -p" showed patches only for single-parent commits on the first-parent chain; the "--first-parent" option has been made to imply "-m". Use "--no-diff-merges" to restore the previous behaviour to omit patches for merge commits. * The commit labels used to explain each side of conflicted hunks placed by the sequencer machinery have been made more readable by humans. * The "--batch-size" option of "git multi-pack-index repack" command is now used to specify that very small packfiles are collected into one until the total size roughly exceeds it. * The recent addition of SHA-256 support is marked as experimental in the documentation. * "git fetch" learned --no-write-fetch-head option to avoid writing the FETCH_HEAD file. * Command line completion (in contrib/) usually omits redundant, deprecated and/or dangerous options from its output; it learned to optionally include all of them. * The output from the "diff" family of the commands had abbreviated object names of blobs involved in the patch, but its length was not affected by the --abbrev option. Now it is. * "git worktree" gained a "repair" subcommand to help users recover after moving the worktrees or repository manually without telling Git. Also, "git init --separate-git-dir" no longer corrupts administrative data related to linked worktrees. * The "--format=" option to the "for-each-ref" command and friends learned a few more tricks, e.g. the ":short" suffix that applies to "objectname" now also can be used for "parent", "tree", etc. * "git worktree add" learns that the "-d" is a synonym to "--detach" option to create a new worktree without being on a branch. * "format-patch --range-diff= ..HEAD" has been taught not to ignore when is a single version. * "add -p" now allows editing paths that were only added in intent. * The
Re: [ANNOUNCE] Git v2.29.0-rc0
Martin Ågren writes: > Minor comments follow. > ... > s/used // (without 'g' flag!) Thanks.
Re: [ANNOUNCE] Git v2.29.0-rc0
Hi Junio,
Thanks for the release candidate!
Minor comments follow.
On Tue, 6 Oct 2020 at 01:00, Junio C Hamano wrote:
> * The final leg of SHA-256 transition plus doc updates. Note that
>there is no inter-operability between SHA-1 and SHA-256
>repositories yet.
I suspect the dash in "inter-operability" should be dropped.
> * Various callers of run_command API has been modernized.
>(merge afbdba391e jc/run-command-use-embedded-args later to maint).
s/has/have/
> * List of options offered and accepted by "git add -i/-p" were
>inconsistent, which have been corrected.
>(merge ce910287e7 pw/add-p-allowed-options-fix later to maint).
>
> * Various callers of run_command API has been modernized.
>(merge afbdba391e jc/run-command-use-embedded-args later to maint).
Here's that entry again from my previous comment.
> * "git status" has trouble showing where it came from by interpreting
>reflog entries that record certain events, e.g. "checkout @{u}", and
>gives a hard/fatal error. Even though it inherently is impossible
>to give a correct answer because the reflog entries lose some
>information (e.g. "@{u}" does not record what branch the user was
>on hence which branch 'the upstream' needs to be computed, and even
>if the record were available, the relationship between branches may
>have changed), at least hide the error to allow "status" show its
>output.
s/show/to &/ ?
> * There is a logic to estimate how many objects are in the
>repository, which is mean to run once per process invocation, but
s/mean/meant/, I think.
> * The "unshelve" subcommand of "git p4" used incorrectly used
s/used // (without 'g' flag!)
Martin
RE: [ANNOUNCE] Git v2.29.0-rc0
On October 5, 2020 6:41 PM, Junio C Hamano wrote: > An early preview release Git v2.29.0-rc0 is now available for > testing at the usual places. It is comprised of 588 non-merge > commits since v2.28.0, contributed by 76 people, 22 of which are > new faces. NonStop build/tests are running. Will let you know the status. Please let me know when you would like git tested with OpenSSL 3.0.0. We are waiting on the GA release otherwise. Regards, Randall
Re: [ANNOUNCE] Git v2.29.0-rc0
On Mon, Oct 5, 2020 at 3:41 PM Junio C Hamano wrote: > > An early preview release Git v2.29.0-rc0 is now available for > testing at the usual places. I've run Bitbucket Server's test matrix over the release candidate. No failures to report. Thanks again for these early milestones! I really appreciate the testing opportunity. Bryan
[ANNOUNCE] Git v2.29.0-rc0
An early preview release Git v2.29.0-rc0 is now available for testing at the usual places. It is comprised of 588 non-merge commits since v2.28.0, contributed by 76 people, 22 of which are new faces. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/testing/ The following public repositories all have a copy of the 'v2.29.0-rc0' tag and the 'master' branch that the tag points at: url = https://kernel.googlesource.com/pub/scm/git/git url = git://repo.or.cz/alt-git.git url = https://github.com/gitster/git New contributors whose contributions weren't in v2.28.0 are as follows. Welcome to the Git development community! Aaron Lipman, Adrian Moennich, Ákos Uzonyi, Antti Keränen, Christian Schlack, Conor Davis, Eric Huber, Evan Gates, Han Xin, Hugo Locurcio, Kyohei Kadota, Lin Sun, Nikita Leonov, Noam Yorav-Raphael, pudinha, Raymond E. Pasco, Ryan Zoeller, Samanta Navarro, Sibi Siddharthan, Simon Legner, Steve Kemp, and Theodore Dubois. Returning contributors who helped this release are as follows. Thanks for your continued support. Ævar Arnfjörð Bjarmason, Alban Gruin, Alex Henrie, Alex Riesen, Andrei Rybak, Beat Bolli, Ben Wijen, brian m. carlson, Christian Couder, Chris Torek, Danny Lin, Denton Liu, Derrick Stolee, Đoàn Trần Công Danh, Drew DeVault, Edmundo Carmona Antoranz, Elijah Newren, Emily Shaffer, Eric Sunshine, Han-Wen Nienhuys, Hariom Verma, Jacob Keller, Jeff Hostetler, Jeff King, Jiang Xin, Johannes Berg, Johannes Schindelin, Johannes Sixt, Jonathan Tan, Junio C Hamano, Kazuhiro Kato, Luke Diamand, Martin Ågren, Matheus Tavares, Matthew Rogers, Michael Forney, Michal Privoznik, Miriam Rubio, Orgad Shaneh, Patrick Steinhardt, Paul Mackerras, Philippe Blain, Phillip Wood, Pranit Bauva, Prathamesh Chavan, René Scharfe, Rohit Ashiwal, Sergey Organov, Shourya Shukla, Stefan Dotterweich, SZEDER Gábor, Taylor Blau, Thomas Guyot-Sionnest, and Роман Донченко. Git 2.29 Release Notes (draft) == Updates since v2.28 --- UI, Workflows & Features * "git help log" has been enhanced by sharing more material from the documentation for the underlying "git rev-list" command. * "git for-each-ref --format=<>" learned %(contents:size). * "git merge" learned to selectively omit " into " at the end of the title of default merge message with merge.suppressDest configuration. * The component to respond to "git fetch" request is made more configurable to selectively allow or reject object filtering specification used for partial cloning. * Stop when "sendmail.*" configuration variables are defined, which could be a mistaken attempt to define "sendemail.*" variables. * The existing backends for "git mergetool" based on variants of vim have been refactored and then support for "nvim" has been added. * "git bisect" learns the "--first-parent" option to find the first breakage along the first-parent chain. * "git log --first-parent -p" showed patches only for single-parent commits on the first-parent chain; the "--first-parent" option has been made to imply "-m". Use "--no-diff-merges" to restore the previous behaviour to omit patches for merge commits. * The commit labels used to explain each side of conflicted hunks placed by the sequencer machinery have been made more readable by humans. * The "--batch-size" option of "git multi-pack-index repack" command is now used to specify that very small packfiles are collected into one until the total size roughly exceeds it. * The recent addition of SHA-256 support is marked as experimental in the documentation. * "git fetch" learned --no-write-fetch-head option to avoid writing the FETCH_HEAD file. * Command line completion (in contrib/) usually omits redundant, deprecated and/or dangerous options from its output; it learned to optionally include all of them. * The output from the "diff" family of the commands had abbreviated object names of blobs involved in the patch, but its length was not affected by the --abbrev option. Now it is. * "git worktree" gained a "repair" subcommand to help users recover after moving the worktrees or repository manually without telling Git. Also, "git init --separate-git-dir" no longer corrupts administrative data related to linked worktrees. * The "--format=" option to the "for-each-ref" command and friends learned a few more tricks, e.g. the ":short" suffix that applies to "objectname" now also can be used for "parent", "tree", etc. * "git worktree add" learns that the "-d" is a synonym to "--detach" option to create a new worktree without being on a branch. * "format-patch --range-diff= ..HEAD" has been taught not to ignore when is a single version. * "add -p" now allows editing paths that were only added in intent. * The 'meld'
