Re: [PATCH v5 0/4] history: add squash subcommand to fold a range

[PATCH 0/2] rebase: add --fixup to fold a range into its oldest commit · Harald Nordgren via GitGitGadget <hidden> · 2026-06-14
[PATCH 1/2] t3415: remove prepare-commit-msg hook after use · Harald Nordgren via GitGitGadget <hidden> · 2026-06-14
[PATCH 2/2] rebase: add --fixup-all to fold a range · Harald Nordgren via GitGitGadget <hidden> · 2026-06-14
Re: [PATCH 0/2] rebase: add --fixup to fold a range into its oldest commit · Junio C Hamano <hidden> · 2026-06-15
Re: [PATCH 0/2] rebase: add --fixup to fold a range into its oldest commit · Harald Nordgren <hidden> · 2026-06-15
Re: [PATCH 0/2] rebase: add --fixup to fold a range into its oldest commit · D. Ben Knoble <hidden> · 2026-06-15
Re: [PATCH 0/2] rebase: add --fixup to fold a range into its oldest commit · Patrick Steinhardt <hidden> · 2026-06-16
Re: [PATCH 0/2] rebase: add --fixup to fold a range into its oldest commit · Harald Nordgren <hidden> · 2026-06-17
[PATCH v2 0/2] rebase: add --squash to fold a range into its first commit · Harald Nordgren via GitGitGadget <hidden> · 2026-06-15
[PATCH v2 1/2] t3415: remove prepare-commit-msg hook after use · Harald Nordgren via GitGitGadget <hidden> · 2026-06-15
[PATCH v2 2/2] rebase: add --squash to fold a range · Harald Nordgren via GitGitGadget <hidden> · 2026-06-15
Re: [PATCH v2 0/2] rebase: add --squash to fold a range into its first commit · Phillip Wood <hidden> · 2026-06-16
Re: [PATCH v2 0/2] rebase: add --squash to fold a range into its first commit · Harald Nordgren <hidden> · 2026-06-17
Re: [PATCH v2 0/2] rebase: add --squash to fold a range into its first commit · Phillip Wood <hidden> · 2026-06-17
[PATCH v3 0/4] history: add squash subcommand to fold a range · Harald Nordgren via GitGitGadget <hidden> · 2026-06-18
[PATCH v3 1/4] history: extract helper for a commit's parent tree · Harald Nordgren via GitGitGadget <hidden> · 2026-06-18
[PATCH v3 2/4] history: give commit_tree_ext a message template · Harald Nordgren via GitGitGadget <hidden> · 2026-06-18
[PATCH v3 3/4] history: add squash subcommand to fold a range · Harald Nordgren via GitGitGadget <hidden> · 2026-06-18
Re: [PATCH v3 3/4] history: add squash subcommand to fold a range · Junio C Hamano <hidden> · 2026-06-18
Re: [PATCH v3 3/4] history: add squash subcommand to fold a range · Junio C Hamano <hidden> · 2026-06-18
Re: [PATCH v3 3/4] history: add squash subcommand to fold a range · D. Ben Knoble <hidden> · 2026-06-18
Re: [PATCH v3 3/4] history: add squash subcommand to fold a range · Patrick Steinhardt <hidden> · 2026-06-19
[PATCH v3 4/4] history: re-edit a squash with every message · Harald Nordgren via GitGitGadget <hidden> · 2026-06-18
Re: [PATCH v3 0/4] history: add squash subcommand to fold a range · D. Ben Knoble <hidden> · 2026-06-18
Re: [PATCH v3 0/4] history: add squash subcommand to fold a range · Junio C Hamano <hidden> · 2026-06-19
Re: [PATCH v3 0/4] history: add squash subcommand to fold a range · Patrick Steinhardt <hidden> · 2026-06-19
Re: [PATCH v3 0/4] history: add squash subcommand to fold a range · Junio C Hamano <hidden> · 2026-06-19
[PATCH v4 0/4] history: add squash subcommand to fold a range · Harald Nordgren via GitGitGadget <hidden> · 2026-06-21
[PATCH v4 1/4] history: extract helper for a commit's parent tree · Harald Nordgren via GitGitGadget <hidden> · 2026-06-21
[PATCH v4 2/4] history: give commit_tree_ext a message template · Harald Nordgren via GitGitGadget <hidden> · 2026-06-21
[PATCH v4 3/4] history: add squash subcommand to fold a range · Harald Nordgren via GitGitGadget <hidden> · 2026-06-21
[PATCH v4 4/4] history: re-edit a squash with every message · Harald Nordgren via GitGitGadget <hidden> · 2026-06-21
Re: [PATCH v4 0/4] history: add squash subcommand to fold a range · Patrick Steinhardt <hidden> · 2026-06-22
Re: [PATCH v4 0/4] history: add squash subcommand to fold a range · Harald Nordgren <hidden> · 2026-06-23
[PATCH v5 0/4] history: add squash subcommand to fold a range · Harald Nordgren via GitGitGadget <hidden> · 2026-06-24
[PATCH v5 1/4] history: extract helper for a commit's parent tree · Harald Nordgren via GitGitGadget <hidden> · 2026-06-24
[PATCH v5 2/4] history: give commit_tree_ext a message template · Harald Nordgren via GitGitGadget <hidden> · 2026-06-24
[PATCH v5 3/4] history: add squash subcommand to fold a range · Harald Nordgren via GitGitGadget <hidden> · 2026-06-24
[PATCH v5 4/4] history: re-edit a squash with every message · Harald Nordgren via GitGitGadget <hidden> · 2026-06-24
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Phillip Wood <hidden> · 2026-06-26
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Harald Nordgren <hidden> · 2026-06-26
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Phillip Wood <hidden> · 2026-06-26
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Junio C Hamano <hidden> · 2026-06-26
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Harald Nordgren <hidden> · 2026-06-26
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Patrick Steinhardt <hidden> · 2026-06-29
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Phillip Wood <hidden> · 2026-06-29
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Junio C Hamano <hidden> · 2026-06-29
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Phillip Wood <hidden> · 2026-07-01
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Harald Nordgren <hidden> · 2026-06-29
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Phillip Wood <hidden> · 2026-06-29
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Harald Nordgren <hidden> · 2026-06-29
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Phillip Wood <hidden> · 2026-06-30
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Harald Nordgren <hidden> · 2026-06-30
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Phillip Wood <hidden> · 2026-07-01
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Junio C Hamano <hidden> · 2026-07-01
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Phillip Wood <hidden> · 2026-07-01
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Junio C Hamano <hidden> · 2026-07-01
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Matt Hunter <hidden> · 2026-06-30
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Harald Nordgren <hidden> · 2026-06-30
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Matt Hunter <hidden> · 2026-06-30
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Phillip Wood <hidden> · 2026-06-30
Re: [PATCH v5 0/4] history: add squash subcommand to fold a range · Harald Nordgren <hidden> · 2026-06-29
[PATCH v6 0/4] history: add squash subcommand to fold a range · Harald Nordgren via GitGitGadget <hidden> · 2026-06-28
[PATCH v6 1/4] history: extract helper for a commit's parent tree · Harald Nordgren via GitGitGadget <hidden> · 2026-06-28
[PATCH v6 2/4] history: give commit_tree_ext a message template · Harald Nordgren via GitGitGadget <hidden> · 2026-06-28
[PATCH v6 3/4] history: add squash subcommand to fold a range · Harald Nordgren via GitGitGadget <hidden> · 2026-06-28
Re: [PATCH v6 3/4] history: add squash subcommand to fold a range · Junio C Hamano <hidden> · 2026-06-29
[PATCH v6 4/4] history: re-edit a squash with every message · Harald Nordgren via GitGitGadget <hidden> · 2026-06-28
Re: [PATCH v6 4/4] history: re-edit a squash with every message · Junio C Hamano <hidden> · 2026-06-29
Re: [PATCH v6 4/4] history: re-edit a squash with every message · Harald Nordgren <hidden> · 2026-06-29
Re: [PATCH v6 4/4] history: re-edit a squash with every message · Junio C Hamano <hidden> · 2026-06-29
Re: [PATCH v6 4/4] history: re-edit a squash with every message · Junio C Hamano <hidden> · 2026-06-29

From: Harald Nordgren <hidden>
Date: 2026-06-29 16:10:16

Yeah, I agree that we should punt on merge commits for now. They are a
can of worms, and I'm not sure that we should just squash them. I would
at least like the user to ask a flag that tells us that it's fine
squashing those.

Do you mean not even handling simple merges that are fully within the
range? I'm already handling those, so remove?


Harald

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help