From: Phillip Wood <phillip.wood123@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: What's cooking in git.git (Dec 2021, #01; Fri, 3)
Date: Mon, 6 Dec 2021 19:13:08 +0000 [thread overview]
Message-ID: <e1aadd47-533c-fd8b-4fae-f64a53c81ec9@gmail.com> (raw)
In-Reply-To: <xmqqh7bpqhf0.fsf@gitster.g>
On 04/12/2021 01:37, Junio C Hamano wrote:
> This is probably the first issue of the "What's cooking" report, in
> which all topics have some sort of description.
>
> That's a small achievement, at least for me.
>
> Even better, each and every topic is annotated with some sort of
> verdict (like "Will discard", "Expecting a reroll", "Will merge to
> 'next'?" etc.). There is no topic in the "Undecided" category when
> this report is fed to "cook -w" script (found in the 'todo' branch).
>
> A handful of topics are added to 'next', and we have about 40 topics
> cooking there. For them, the future is automated---they spend about
> a week in 'next', and if we find issues in them, we incrementally
> improve them, or get merged to 'master'.
>
> Then we have about a dozen topics that are marked for 'next' (please
> raise your hand if you have objection before a real damage is done),
> and 8 more that may be ready for 'next' (please raise your hand if
> you want to nudge them in either direction, for or against).
>[...]
> * pw/fix-some-issues-in-reset-head (2021-10-01) 12 commits
> - rebase -m: don't fork git checkout
> - rebase --apply: set ORIG_HEAD correctly
> - rebase --apply: fix reflog
> - reset_head(): take struct rebase_head_opts
> - rebase: cleanup reset_head() calls
> - reset_head(): make default_reflog_action optional
> - reset_head(): factor out ref updates
> - reset_head(): remove action parameter
> - reset_head(): don't run checkout hook if there is an error
> - reset_head(): fix checkout
> - rebase: factor out checkout for up to date branch
> - Merge branch 'pw/rebase-of-a-tag-fix' into pw/fix-some-issues-in-reset-head
>
> Fix "some issues" in a helper function reset_head().
>
> Will discard.
> This needs a lot better explanation, including what the issues are,
> which codepaths the helper is used in and to do what, and tests to
> protect the fixes.
> source: <pull.1049.git.1633082702.gitgitgadget@gmail.com>
I've got a re-roll which I think is almost ready but feel free to drop
it in the meantime.
> * pw/diff-color-moved-fix (2021-10-27) 15 commits
> - diff --color-moved: intern strings
> - diff: use designated initializers for emitted_diff_symbol
> - diff --color-moved-ws=allow-indentation-change: improve hash lookups
> - diff --color-moved: stop clearing potential moved blocks
> - diff --color-moved: shrink potential moved blocks as we go
> - diff --color-moved: unify moved block growth functions
> - diff --color-moved: call comparison function directly
> - diff --color-moved-ws=allow-indentation-change: simplify and optimize
> - diff: simplify allow-indentation-change delta calculation
> - diff --color-moved: avoid false short line matches and bad zerba coloring
> - diff --color-moved=zebra: fix alternate coloring
> - diff --color-moved: rewind when discarding pmb
> - diff --color-moved: factor out function
> - diff --color-moved: clear all flags on blocks that are too short
> - diff --color-moved: add perf tests
>
> Long-overdue correctness and performance update to "diff
> --color-moved" feature.
>
> Need to pick up the reroll before merging to 'next'.
> cf. <pull.981.v4.git.1637056178.gitgitgadget@gmail.com>
Dscho spotted a typo which I was going to correct with a re-roll but
I've been holding off in case he has time to read the rest of the series.
Best Wishes
Phillip
next prev parent reply other threads:[~2021-12-06 19:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 1:37 What's cooking in git.git (Dec 2021, #01; Fri, 3) Junio C Hamano
2021-12-06 19:13 ` Phillip Wood [this message]
2021-12-06 19:24 ` Junio C Hamano
2021-12-08 12:42 ` Johannes Schindelin
2021-12-09 1:02 ` Junio C Hamano
2021-12-09 10:39 ` Phillip Wood
2021-12-07 6:00 ` en/keep-cwd (Was: Re: What's cooking in git.git (Dec 2021, #01; Fri, 3)) Elijah Newren
2021-12-07 9:17 ` Ævar Arnfjörð Bjarmason
2021-12-07 20:33 ` Elijah Newren
2021-12-07 18:26 ` en/keep-cwd Junio C Hamano
2021-12-08 12:46 ` en/keep-cwd (Was: Re: What's cooking in git.git (Dec 2021, #01; Fri, 3)) Johannes Schindelin
2021-12-07 15:54 ` What's cooking in git.git (Dec 2021, #01; Fri, 3) Derrick Stolee
2021-12-07 19:37 ` cf/fetch-set-upstream-while-detached (was: What's cooking in git.git (Dec 2021, #01; Fri, 3)) Ævar Arnfjörð Bjarmason
2021-12-07 20:41 ` cf/fetch-set-upstream-while-detached Junio C Hamano
2021-12-07 22:04 ` [PATCH v5] pull, fetch: fix segfault in --set-upstream option Ævar Arnfjörð Bjarmason
-- strict thread matches above, loose matches on Subject: below --
2021-12-04 1:37 What's cooking in git.git (Dec 2021, #01; Fri, 3) Junio C Hamano
2021-12-07 1:08 ` Junio C Hamano
2021-12-07 16:21 ` Derrick Stolee
2021-12-07 17:25 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e1aadd47-533c-fd8b-4fae-f64a53c81ec9@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=phillip.wood@dunelm.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).