git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Harald Nordgren via GitGitGadget <gitgitgadget@gmail.com>
Date
Jun 21, 2026, 05:53 UTC
Message-ID
<pull.2337.v4.git.git.1782021195.gitgitgadget@gmail.com>
In-Reply-To
<pull.2337.v3.git.git.1781810226.gitgitgadget@gmail.com>
Adds git history squash <revision-range> to fold a range of commits.
Changes in v4:
 * git history squash now detects when another ref points at a commit inside
   the range being folded and refuses, with an advice.historyUpdateRefs hint
   to use --update-refs=head.
 * A merge inside the range is folded fine as long as the range has a single
   base; a range with merge commit at the tip or base also folds correctly.
   Only a range with more than one base is rejected.
Changes in v3:
 * Moved the feature out of git rebase and into a new git history squash
   <revision-range> subcommand, per the list discussion. git rebase --squash
   is dropped.
 * Takes an arbitrary range (git history squash @~3.., git history squash
   @~5..@~2), folding it into the oldest commit and replaying any
   descendants on top.
 * Implemented as a single tree operation rather than picking each commit,
   so there are no repeated conflict stops (addresses Phillip's efficiency
   point).
 * A merge inside the range is folded fine, only a range with more than one
   base is rejected.
 * --reedit-message seeds the editor with every folded-in message, not just
   the oldest.
Harald Nordgren (4):
  history: extract helper for a commit's parent tree
  history: give commit_tree_ext a message template
  history: add squash subcommand to fold a range
  history: re-edit a squash with every message
 Documentation/config/advice.adoc |   4 +
 Documentation/git-history.adoc   |  26 +++
 advice.c                         |   1 +
 advice.h                         |   1 +
 builtin/history.c                | 328 +++++++++++++++++++++++++----
 t/meson.build                    |   1 +
 t/t3455-history-squash.sh        | 340 +++++++++++++++++++++++++++++++
 7 files changed, 663 insertions(+), 38 deletions(-)
 create mode 100755 t/t3455-history-squash.sh
base-commit: 8d96f09e9245ddf80c1981476fcbac8c4bb4125f
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2337%2FHaraldNordgren%2Frebase-fixup-fold-v4
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2337/HaraldNordgren/rebase-fixup-fold-v4
Pull-Request: https://github.com/git/git/pull/2337
Range-diff vs v3:
 1:  1e31474ef6 = 1:  fc2801c0b1 history: extract helper for a commit's parent tree
 2:  498da64046 = 2:  ee591e83b4 history: give commit_tree_ext a message template
 3:  66b2f49fb4 ! 3:  80bfea642e history: add squash subcommand to fold a range
     @@ Commit message
          other commit, but the range must have a single base, so a range with
          more than one entry point is rejected.
      
     +    The folded commits leave the history, so by default the command refuses
     +    when another ref points at one of them. Use "--update-refs=head" to
     +    rewrite only the current branch and leave those refs untouched.
     +
          Inspired-by: Sergey Chernov <serega.morph@gmail.com>
          Signed-off-by: Harald Nordgren <haraldnordgren@gmail.com>
      
     + ## Documentation/config/advice.adoc ##
     +@@ Documentation/config/advice.adoc: all advice messages.
     + 	forceDeleteBranch::
     + 		Shown when the user tries to delete a not fully merged
     + 		branch without the force option set.
     ++	historyUpdateRefs::
     ++		Shown when `git history squash` refuses because a ref points
     ++		into the range being folded, to tell the user about
     ++		`--update-refs=head`.
     + 	ignoredHook::
     + 		Shown when a hook is ignored because the hook is not
     + 		set as executable.
     +
       ## Documentation/git-history.adoc ##
      @@ Documentation/git-history.adoc: SYNOPSIS
       git history fixup <commit> [--dry-run] [--update-refs=(branches|head)] [--reedit-message] [--empty=(drop|keep|abort)]
     @@ Documentation/git-history.adoc: linkgit:gitglossary[7].
      +folded like any other, but the range must have a single base, so a range
      +that reaches more than one entry point (for example a side branch that
      +forked before the range and was later merged into it) is rejected.
     +++
     ++The folded commits disappear from the history, so with the default
     ++`--update-refs=branches` the command refuses when another ref points at
     ++one of them. Rerun with `--update-refs=head` to rewrite only the current
     ++branch and leave those refs pointing at the old commits.
      +
       OPTIONS
       -------
       
      
     + ## advice.c ##
     +@@ advice.c: static struct {
     + 	[ADVICE_FETCH_SHOW_FORCED_UPDATES]		= { "fetchShowForcedUpdates" },
     + 	[ADVICE_FORCE_DELETE_BRANCH]			= { "forceDeleteBranch" },
     + 	[ADVICE_GRAFT_FILE_DEPRECATED]			= { "graftFileDeprecated" },
     ++	[ADVICE_HISTORY_UPDATE_REFS]			= { "historyUpdateRefs" },
     + 	[ADVICE_IGNORED_HOOK]				= { "ignoredHook" },
     + 	[ADVICE_IMPLICIT_IDENTITY]			= { "implicitIdentity" },
     + 	[ADVICE_MERGE_CONFLICT]				= { "mergeConflict" },
     +
     + ## advice.h ##
     +@@ advice.h: enum advice_type {
     + 	ADVICE_FETCH_SHOW_FORCED_UPDATES,
     + 	ADVICE_FORCE_DELETE_BRANCH,
     + 	ADVICE_GRAFT_FILE_DEPRECATED,
     ++	ADVICE_HISTORY_UPDATE_REFS,
     + 	ADVICE_IGNORED_HOOK,
     + 	ADVICE_IMPLICIT_IDENTITY,
     + 	ADVICE_MERGE_CONFLICT,
     +
       ## builtin/history.c ##
     +@@
     + #define USE_THE_REPOSITORY_VARIABLE
     + 
     + #include "builtin.h"
     ++#include "advice.h"
     + #include "cache-tree.h"
     + #include "commit.h"
     + #include "commit-reach.h"
      @@
       	N_("git history reword <commit> [--dry-run] [--update-refs=(branches|head)]")
       #define GIT_HISTORY_SPLIT_USAGE \
     @@ builtin/history.c: out:
      +				const char *range,
      +				struct commit **base_out,
      +				struct commit **oldest_out,
     -+				struct commit **tip_out)
     ++				struct commit **tip_out,
     ++				struct oidset *interior_out)
      +{
      +	struct rev_info revs;
      +	struct commit *commit, *base = NULL, *oldest = NULL, *tip = NULL;
     @@ builtin/history.c: out:
      +		}
      +		if (!oldest)
      +			oldest = commit;
     ++		if (tip)
     ++			oidset_insert(interior_out, &tip->object.oid);
      +		tip = commit;
      +	}
      +
     @@ builtin/history.c: out:
      +	return ret;
      +}
      +
     ++struct interior_ref_cb {
     ++	const struct oidset *interior;
     ++	const char *name;
     ++};
     ++
     ++static int find_interior_ref(const struct reference *ref, void *cb_data)
     ++{
     ++	struct interior_ref_cb *data = cb_data;
     ++
     ++	if (oidset_contains(data->interior, ref->oid)) {
     ++		data->name = xstrdup(ref->name);
     ++		return 1;
     ++	}
     ++
     ++	return 0;
     ++}
     ++
      +static int cmd_history_squash(int argc,
      +			      const char **argv,
      +			      const char *prefix,
     @@ builtin/history.c: out:
      +		OPT_END(),
      +	};
      +	struct strbuf reflog_msg = STRBUF_INIT;
     ++	struct oidset interior = OIDSET_INIT;
      +	struct commit *base, *oldest, *tip, *rewritten;
      +	const struct object_id *base_tree_oid, *tip_tree_oid;
      +	struct commit_list *parents = NULL;
     @@ builtin/history.c: out:
      +	if (action == REF_ACTION_DEFAULT)
      +		action = REF_ACTION_BRANCHES;
      +
     -+	ret = resolve_squash_range(repo, argv[0], &base, &oldest, &tip);
     ++	ret = resolve_squash_range(repo, argv[0], &base, &oldest, &tip,
     ++				   &interior);
      +	if (ret < 0)
      +		goto out;
      +
     ++	if (action == REF_ACTION_BRANCHES) {
     ++		struct interior_ref_cb cb = { .interior = &interior };
     ++
     ++		refs_for_each_ref(get_main_ref_store(repo),
     ++				  find_interior_ref, &cb);
     ++		if (cb.name) {
     ++			ret = error(_("'%s' points into the squashed range"),
     ++				    cb.name);
     ++			advise_if_enabled(ADVICE_HISTORY_UPDATE_REFS,
     ++					  _("Use --update-refs=head to rewrite only "
     ++					    "the current branch and leave such refs "
     ++					    "untouched."));
     ++			free((char *)cb.name);
     ++			goto out;
     ++		}
     ++	}
     ++
      +	ret = setup_revwalk(repo, action, tip, &revs);
      +	if (ret < 0)
      +		goto out;
     @@ builtin/history.c: out:
      +
      +out:
      +	strbuf_release(&reflog_msg);
     ++	oidset_clear(&interior);
      +	commit_list_free(parents);
      +	release_revisions(&revs);
      +	return ret;
     @@ t/meson.build: integration_tests = [
         't3451-history-reword.sh',
         't3452-history-split.sh',
         't3453-history-fixup.sh',
     -+  't3454-history-squash.sh',
     ++  't3455-history-squash.sh',
         't3500-cherry.sh',
         't3501-revert-cherry-pick.sh',
         't3502-cherry-pick-merge.sh',
      
     - ## t/t3454-history-squash.sh (new) ##
     + ## t/t3455-history-squash.sh (new) ##
      @@
      +#!/bin/sh
      +
     @@ t/t3454-history-squash.sh (new)
      +test_expect_success 'setup linear history touching two files' '
      +	test_commit base file a &&
      +	git tag start &&
     -+	test_commit one other x &&
     -+	test_commit two file c &&
     ++	test_commit --no-tag one other x &&
     ++	test_commit --no-tag two file c &&
      +	test_commit three file d
      +'
      +
     @@ t/t3454-history-squash.sh (new)
      +
      +test_expect_success 'reuses the message of a fixup! commit in the range' '
      +	git reset --hard start &&
     -+	test_commit reg1 file b &&
     ++	test_commit --no-tag reg1 file b &&
      +	git commit --allow-empty -m "fixup! reg1" &&
      +	test_commit reg2 file c &&
      +
     @@ t/t3454-history-squash.sh (new)
      +test_expect_success 'preserves authorship of the oldest commit' '
      +	git reset --hard start &&
      +	GIT_AUTHOR_NAME=Squasher GIT_AUTHOR_EMAIL=squash@example.com \
     -+		test_commit oldest file b &&
     ++		test_commit --no-tag oldest file b &&
      +	test_commit newest file c &&
      +
      +	git history squash start.. &&
     @@ t/t3454-history-squash.sh (new)
      +test_expect_success '--dry-run predicts the rewrite without performing it' '
      +	git reset --hard three &&
      +	head_before=$(git rev-parse HEAD) &&
     ++	tip_tree=$(git rev-parse HEAD^{tree}) &&
      +
      +	git history squash --dry-run start.. >out &&
     -+	grep "^update refs/heads/" out >update &&
     -+	predicted=$(awk "{print \$3}" update) &&
     ++	predicted=$(awk "/^update refs\/heads\// {print \$3}" out) &&
      +	test_cmp_rev "$head_before" HEAD &&
      +
      +	git history squash start.. &&
     -+	test "$predicted" = "$(git rev-parse HEAD)"
     ++	test "$predicted" = "$(git rev-parse HEAD)" &&
     ++	git rev-list --count start..HEAD >count &&
     ++	echo 1 >expect &&
     ++	test_cmp expect count &&
     ++	test_cmp_rev start HEAD^ &&
     ++	test "$tip_tree" = "$(git rev-parse HEAD^{tree})"
      +'
      +
      +test_expect_success '--update-refs=head only moves HEAD' '
     @@ t/t3454-history-squash.sh (new)
      +	test_cmp_rev "$other_before" other
      +'
      +
     -+test_expect_success '--update-refs=branches moves a branch pointing into the range' '
     ++test_expect_success 'refuses to fold a range a ref points into' '
     ++	git reset --hard three &&
     ++	git branch -f mid HEAD~1 &&
     ++	head_before=$(git rev-parse HEAD) &&
     ++
     ++	test_must_fail git history squash start.. 2>err &&
     ++	test_grep "error: .* points into the squashed range" err &&
     ++	test_grep "hint: .*--update-refs=head" err &&
     ++	test_cmp_rev "$head_before" HEAD &&
     ++
     ++	git branch -D mid
     ++'
     ++
     ++test_expect_success 'advice.historyUpdateRefs silences the hint' '
     ++	git reset --hard three &&
     ++	git branch -f mid HEAD~1 &&
     ++
     ++	test_must_fail git -c advice.historyUpdateRefs=false \
     ++		history squash start.. 2>err &&
     ++	test_grep "points into the squashed range" err &&
     ++	test_grep ! "hint:" err &&
     ++
     ++	git branch -D mid
     ++'
     ++
     ++test_expect_success '--update-refs=head folds past a ref pointing into the range' '
      +	git reset --hard three &&
     -+	git branch -f mid HEAD~2 &&
     ++	git branch -f mid HEAD~1 &&
      +	mid_before=$(git rev-parse mid) &&
      +
     -+	git history squash start..@~1 &&
     ++	git history squash --update-refs=head start.. &&
      +
     ++	git rev-list --count start..HEAD >count &&
     ++	echo 1 >expect &&
     ++	test_cmp expect count &&
      +	test_cmp_rev "$mid_before" mid &&
     -+	test_commit_message mid -m one
     ++
     ++	git branch -D mid
     ++'
     ++
     ++test_expect_success 'refuses to fold a range a tag points into' '
     ++	git reset --hard three &&
     ++	git tag -f mark HEAD~1 &&
     ++	head_before=$(git rev-parse HEAD) &&
     ++
     ++	test_must_fail git history squash start.. 2>err &&
     ++	test_grep "refs/tags/mark" err &&
     ++	test_grep "points into the squashed range" err &&
     ++	test_cmp_rev "$head_before" HEAD &&
     ++
     ++	git tag -d mark
      +'
      +
      +test_expect_success 'squashes a range whose internal merge has a single base' '
      +	git reset --hard start &&
     -+	test_commit before-side file b &&
     ++	test_commit --no-tag before-side file b &&
      +	git checkout -b inner-side &&
     -+	test_commit on-inner-side inner x &&
     ++	test_commit --no-tag on-inner-side inner x &&
      +	git checkout - &&
     -+	test_commit after-side file c &&
     ++	test_commit --no-tag after-side file c &&
      +	git merge --no-ff -m merge inner-side &&
     -+	test_commit after-merge file d &&
     ++	git branch -D inner-side &&
     ++	test_commit --no-tag after-merge file d &&
      +	tip_tree=$(git rev-parse HEAD^{tree}) &&
      +
      +	git history squash start.. &&
     @@ t/t3454-history-squash.sh (new)
      +	test_path_is_file inner
      +'
      +
     ++test_expect_success 'folds a range whose tip is a merge commit' '
     ++	git reset --hard start &&
     ++	test_commit --no-tag tipmerge-base file b &&
     ++	git checkout -b tipmerge-side &&
     ++	test_commit --no-tag tipmerge-side side x &&
     ++	git checkout - &&
     ++	test_commit --no-tag tipmerge-main file c &&
     ++	git merge --no-ff -m "merge tipmerge-side" tipmerge-side &&
     ++	git branch -D tipmerge-side &&
     ++	tip_tree=$(git rev-parse HEAD^{tree}) &&
     ++
     ++	git history squash start.. &&
     ++
     ++	git rev-list --count start..HEAD >count &&
     ++	echo 1 >expect &&
     ++	test_cmp expect count &&
     ++	test "$tip_tree" = "$(git rev-parse HEAD^{tree})" &&
     ++	test_path_is_file side
     ++'
     ++
     ++test_expect_success 'folds a range whose base is a merge commit' '
     ++	git reset --hard start &&
     ++	git checkout -b basemerge-side &&
     ++	test_commit --no-tag basemerge-side side x &&
     ++	git checkout - &&
     ++	test_commit --no-tag basemerge-main file b &&
     ++	git merge --no-ff -m "merge basemerge-side" basemerge-side &&
     ++	git branch -D basemerge-side &&
     ++	base=$(git rev-parse HEAD) &&
     ++	test_commit --no-tag basemerge-one file c &&
     ++	test_commit --no-tag basemerge-two file d &&
     ++	tip_tree=$(git rev-parse HEAD^{tree}) &&
     ++
     ++	git history squash "$base.." &&
     ++
     ++	git rev-list --count "$base..HEAD" >count &&
     ++	echo 1 >expect &&
     ++	test_cmp expect count &&
     ++	test_cmp_rev "$base" HEAD^ &&
     ++	test "$tip_tree" = "$(git rev-parse HEAD^{tree})"
     ++'
     ++
      +test_expect_success 'refuses to squash a range with more than one base' '
      +	git reset --hard start &&
      +	head_before=$(git rev-parse HEAD) &&
 4:  43e4270614 ! 4:  85c7817d7e history: re-edit a squash with every message
     @@ Documentation/git-history.adoc: history squash @~3..` folds the three most recen
       forked before the range and was later merged into it) is rejected.
      
       ## builtin/history.c ##
     -@@ builtin/history.c: out:
     - 	return ret;
     +@@ builtin/history.c: static int find_interior_ref(const struct reference *ref, void *cb_data)
     + 	return 0;
       }
       
      +static int build_squash_message(struct repository *repo,
     @@ builtin/history.c: static int cmd_history_squash(int argc,
       	};
       	struct strbuf reflog_msg = STRBUF_INIT;
      +	struct strbuf message = STRBUF_INIT;
     + 	struct oidset interior = OIDSET_INIT;
       	struct commit *base, *oldest, *tip, *rewritten;
       	const struct object_id *base_tree_oid, *tip_tree_oid;
     - 	struct commit_list *parents = NULL;
      @@ builtin/history.c: static int cmd_history_squash(int argc,
     - 	if (ret < 0)
     - 		goto out;
     + 		}
     + 	}
       
      +	if (flags & COMMIT_TREE_EDIT_MESSAGE) {
      +		ret = build_squash_message(repo, base, tip, &message);
     @@ builtin/history.c: static int cmd_history_squash(int argc,
       out:
       	strbuf_release(&reflog_msg);
      +	strbuf_release(&message);
     + 	oidset_clear(&interior);
       	commit_list_free(parents);
       	release_revisions(&revs);
     - 	return ret;
      
     - ## t/t3454-history-squash.sh ##
     -@@ t/t3454-history-squash.sh: test_expect_success 'preserves authorship of the oldest commit' '
     + ## t/t3455-history-squash.sh ##
     +@@ t/t3455-history-squash.sh: test_expect_success 'preserves authorship of the oldest commit' '
       	test_cmp expect actual
       '
       
     @@ t/t3454-history-squash.sh: test_expect_success 'preserves authorship of the olde
      +	echo b >file &&
      +	git add file &&
      +	git commit -m "re-one subject" -m "re-one body line" &&
     -+	test_commit re-two file c &&
     ++	test_commit --no-tag re-two file c &&
      +	test_commit re-three file d &&
      +
      +	write_script editor <<-\EOF &&
     @@ t/t3454-history-squash.sh: test_expect_success 'preserves authorship of the olde
      +	test_set_editor "$(pwd)/editor" &&
      +	git history squash --reedit-message start.. &&
      +
     -+	grep "re-one subject" buffer &&
     -+	grep "re-one body line" buffer &&
     -+	grep re-two buffer &&
     -+	grep re-three buffer &&
     ++	test_grep "re-one subject" buffer &&
     ++	test_grep "re-one body line" buffer &&
     ++	test_grep re-two buffer &&
     ++	test_grep re-three buffer &&
      +	git log --format="%s" -1 >actual &&
      +	echo combined >expect &&
      +	test_cmp expect actual
-- 
gitgitgadget
Previous: Junio C HamanoNext: Harald Nordgren via GitGitGadget
Message 28 of 185 in “rebase: add --fixup to fold a range into its oldest commit”
  1. 0/2 rebase: add --fixup to fold a range into its oldest commitHarald Nordgren via GitGitGadget, Jun 14, 2026
  2. 1/2 t3415: remove prepare-commit-msg hook after useHarald Nordgren via GitGitGadget, Jun 14, 2026
  3. 2/2 rebase: add --fixup-all to fold a rangeHarald Nordgren via GitGitGadget, Jun 14, 2026
  4. Junio C HamanoJun 15, 2026
  5. Harald NordgrenJun 15, 2026
  6. D. Ben KnobleJun 15, 2026
  7. Patrick SteinhardtJun 16, 2026
  8. Harald NordgrenJun 17, 2026
  9. 0/2 rebase: add --squash to fold a range into its first commitHarald Nordgren via GitGitGadget, Jun 15, 2026
  10. 1/2 t3415: remove prepare-commit-msg hook after useHarald Nordgren via GitGitGadget, Jun 15, 2026
  11. 2/2 rebase: add --squash to fold a rangeHarald Nordgren via GitGitGadget, Jun 15, 2026
  12. Phillip WoodJun 16, 2026
  13. Harald NordgrenJun 17, 2026
  14. Phillip WoodJun 17, 2026
  15. 0/4 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jun 18, 2026
  16. 1/4 history: extract helper for a commit's parent treeHarald Nordgren via GitGitGadget, Jun 18, 2026
  17. 2/4 history: give commit_tree_ext a message templateHarald Nordgren via GitGitGadget, Jun 18, 2026
  18. 3/4 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jun 18, 2026
  19. Junio C HamanoJun 18, 2026
  20. Junio C HamanoJun 18, 2026
  21. D. Ben KnobleJun 18, 2026
  22. Patrick SteinhardtJun 19, 2026
  23. 4/4 history: re-edit a squash with every messageHarald Nordgren via GitGitGadget, Jun 18, 2026
  24. D. Ben KnobleJun 18, 2026
  25. Junio C HamanoJun 19, 2026
  26. Patrick SteinhardtJun 19, 2026
  27. Junio C HamanoJun 19, 2026
  28. 0/4 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jun 21, 2026
  29. 1/4 history: extract helper for a commit's parent treeHarald Nordgren via GitGitGadget, Jun 21, 2026
  30. 2/4 history: give commit_tree_ext a message templateHarald Nordgren via GitGitGadget, Jun 21, 2026
  31. 3/4 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jun 21, 2026
  32. 4/4 history: re-edit a squash with every messageHarald Nordgren via GitGitGadget, Jun 21, 2026
  33. Patrick SteinhardtJun 22, 2026
  34. Harald NordgrenJun 23, 2026
  35. 0/4 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jun 24, 2026
  36. 1/4 history: extract helper for a commit's parent treeHarald Nordgren via GitGitGadget, Jun 24, 2026
  37. 2/4 history: give commit_tree_ext a message templateHarald Nordgren via GitGitGadget, Jun 24, 2026
  38. 3/4 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jun 24, 2026
  39. 4/4 history: re-edit a squash with every messageHarald Nordgren via GitGitGadget, Jun 24, 2026
  40. Phillip WoodJun 26, 2026
  41. Harald NordgrenJun 26, 2026
  42. Phillip WoodJun 26, 2026
  43. Junio C HamanoJun 26, 2026
  44. Harald NordgrenJun 26, 2026
  45. Patrick SteinhardtJun 29, 2026
  46. Phillip WoodJun 29, 2026
  47. Junio C HamanoJun 29, 2026
  48. Phillip WoodJul 1, 2026
  49. Harald NordgrenJun 29, 2026
  50. Phillip WoodJun 29, 2026
  51. Harald NordgrenJun 29, 2026
  52. Phillip WoodJun 30, 2026
  53. Harald NordgrenJun 30, 2026
  54. Phillip WoodJul 1, 2026
  55. Junio C HamanoJul 1, 2026
  56. Phillip WoodJul 1, 2026
  57. Junio C HamanoJul 1, 2026
  58. Phillip WoodJul 2, 2026
  59. Matt HunterJun 30, 2026
  60. Harald NordgrenJun 30, 2026
  61. Matt HunterJun 30, 2026
  62. Phillip WoodJun 30, 2026
  63. Patrick SteinhardtJul 2, 2026
  64. Junio C HamanoJul 2, 2026
  65. Harald NordgrenJun 29, 2026
  66. 0/4 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jun 28, 2026
  67. 1/4 history: extract helper for a commit's parent treeHarald Nordgren via GitGitGadget, Jun 28, 2026
  68. 2/4 history: give commit_tree_ext a message templateHarald Nordgren via GitGitGadget, Jun 28, 2026
  69. 3/4 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jun 28, 2026
  70. Junio C HamanoJun 29, 2026
  71. 4/4 history: re-edit a squash with every messageHarald Nordgren via GitGitGadget, Jun 28, 2026
  72. Junio C HamanoJun 29, 2026
  73. Harald NordgrenJun 29, 2026
  74. Junio C HamanoJun 29, 2026
  75. Junio C HamanoJun 29, 2026
  76. 0/5 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jul 6, 2026
  77. 1/5 history: extract helper for a commit's parent treeHarald Nordgren via GitGitGadget, Jul 6, 2026
  78. 2/5 history: give commit_tree_ext a message templateHarald Nordgren via GitGitGadget, Jul 6, 2026
  79. 3/5 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jul 6, 2026
  80. 4/5 sequencer: extract helpers for the squash message markersHarald Nordgren via GitGitGadget, Jul 6, 2026
  81. 5/5 history: re-edit a squash with every messageHarald Nordgren via GitGitGadget, Jul 6, 2026
  82. Phillip WoodJul 6, 2026
  83. Harald NordgrenJul 7, 2026
  84. Harald NordgrenJul 7, 2026
  85. Phillip WoodJul 7, 2026
  86. Phillip WoodJul 7, 2026
  87. Junio C HamanoJul 6, 2026
  88. 0/5 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jul 10, 2026
  89. 1/5 history: extract helper for a commit's parent treeHarald Nordgren via GitGitGadget, Jul 10, 2026
  90. 2/5 history: give commit_tree_ext a message templateHarald Nordgren via GitGitGadget, Jul 10, 2026
  91. 3/5 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jul 10, 2026
  92. 4/5 sequencer: share the squash message marker helpers and flagsHarald Nordgren via GitGitGadget, Jul 10, 2026
  93. 5/5 history: re-edit a squash with every messageHarald Nordgren via GitGitGadget, Jul 10, 2026
  94. Matt HunterJul 14, 2026
  95. Harald NordgrenJul 14, 2026
  96. Harald NordgrenJul 14, 2026
  97. Ben KnobleJul 14, 2026
  98. Junio C HamanoJul 14, 2026
  99. 0/5 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jul 15, 2026
  100. 1/5 history: extract helper for a commit's parent treeHarald Nordgren via GitGitGadget, Jul 15, 2026
  101. 2/5 history: give commit_tree_ext a message templateHarald Nordgren via GitGitGadget, Jul 15, 2026
  102. 3/5 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jul 15, 2026
  103. Matt HunterJul 18, 2026
  104. Harald NordgrenJul 18, 2026
  105. 4/5 sequencer: share the squash message marker helpers and flagsHarald Nordgren via GitGitGadget, Jul 15, 2026
  106. 5/5 history: re-edit a squash with every messageHarald Nordgren via GitGitGadget, Jul 15, 2026
  107. Matt HunterJul 18, 2026
  108. Harald NordgrenJul 18, 2026
  109. 0/5 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jul 20, 2026
  110. 1/5 history: extract helper for a commit's parent treeHarald Nordgren via GitGitGadget, Jul 20, 2026
  111. 2/5 history: give commit_tree_ext a message templateHarald Nordgren via GitGitGadget, Jul 20, 2026
  112. 3/5 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Jul 20, 2026
  113. Phillip WoodAug 3, 2026
  114. 1/3 fixup! history: add squash subcommand to fold a rangePhillip Wood, Aug 3, 2026
  115. 2/3 fixup! history: add squash subcommand to fold a rangePhillip Wood, Aug 3, 2026
  116. 3/3 fixup! history: add squash subcommand to fold a rangePhillip Wood, Aug 3, 2026
  117. 4/3 fixup! history: add squash subcommand to fold a rangePhillip Wood, Aug 3, 2026
  118. 5/3 fixup! history: add squash subcommand to fold a rangePhillip Wood, Aug 3, 2026
  119. 6/3 fixup! history: add squash subcommand to fold a rangePhillip Wood, Aug 3, 2026
  120. 7/3 fixup! history: add squash subcommand to fold a rangePhillip Wood, Aug 3, 2026
  121. Harald NordgrenAug 3, 2026
  122. Phillip WoodAug 4, 2026
  123. Junio C HamanoAug 4, 2026
  124. Harald NordgrenAug 4, 2026
  125. Harald NordgrenAug 4, 2026
  126. Tuomas AholaAug 7, 2026
  127. Junio C HamanoAug 4, 2026
  128. Phillip WoodAug 7, 2026
  129. Harald NordgrenAug 7, 2026
  130. Kristoffer HaugsbakkAug 6, 2026
  131. 4/5 sequencer: share the squash message marker helpers and flagsHarald Nordgren via GitGitGadget, Jul 20, 2026
  132. 5/5 history: re-edit a squash with every messageHarald Nordgren via GitGitGadget, Jul 20, 2026
  133. Matt HunterJul 21, 2026
  134. 0/4 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Aug 1, 2026
  135. 1/4 history: extract helper for a commit's parent treeHarald Nordgren via GitGitGadget, Aug 1, 2026
  136. 2/4 history: give commit_tree_ext a message templateHarald Nordgren via GitGitGadget, Aug 1, 2026
  137. 3/4 sequencer: share the squash message marker helpers and flagsHarald Nordgren via GitGitGadget, Aug 1, 2026
  138. 4/4 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Aug 1, 2026
  139. 0/4 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Aug 4, 2026
  140. 1/4 history: extract helper for a commit's parent treeHarald Nordgren via GitGitGadget, Aug 4, 2026
  141. 2/4 history: give commit_tree_ext a message templateHarald Nordgren via GitGitGadget, Aug 4, 2026
  142. 3/4 sequencer: share the squash message marker helpers and flagsHarald Nordgren via GitGitGadget, Aug 4, 2026
  143. 4/4 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Aug 4, 2026
  144. 0/8 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Aug 7, 2026
  145. 1/8 history: extract helper for a commit's parent treeHarald Nordgren via GitGitGadget, Aug 7, 2026
  146. 2/8 history: give commit_tree_ext a message templateHarald Nordgren via GitGitGadget, Aug 7, 2026
  147. 3/8 sequencer: share the squash message marker helpers and flagsHarald Nordgren via GitGitGadget, Aug 7, 2026
  148. 4/8 history: add skeleton for squash subcommandHarald Nordgren via GitGitGadget, Aug 7, 2026
  149. 5/8 history: validate squash revision rangesHarald Nordgren via GitGitGadget, Aug 7, 2026
  150. 6/8 history: protect branches when squashing a rangeHarald Nordgren via GitGitGadget, Aug 7, 2026
  151. 7/8 history: create squashed commits without editingHarald Nordgren via GitGitGadget, Aug 7, 2026
  152. Junio C HamanoAug 13, 2026
  153. Junio C HamanoAug 13, 2026
  154. Phillip WoodAug 17, 2026
  155. Junio C HamanoAug 17, 2026
  156. Junio C HamanoAug 17, 2026
  157. Junio C HamanoAug 17, 2026
  158. Junio C HamanoAug 17, 2026
  159. Harald NordgrenAug 17, 2026
  160. Kristoffer HaugsbakkAug 17, 2026
  161. 8/8 history: support editing squashed commit messagesHarald Nordgren via GitGitGadget, Aug 7, 2026
  162. 0/8 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Aug 20, 2026
  163. 1/8 history: extract helper for a commit's parent treeHarald Nordgren via GitGitGadget, Aug 20, 2026
  164. 2/8 history: give commit_tree_ext a message templateHarald Nordgren via GitGitGadget, Aug 20, 2026
  165. 3/8 sequencer: share the squash message marker helpers and flagsHarald Nordgren via GitGitGadget, Aug 20, 2026
  166. 4/8 history: add skeleton for squash subcommandHarald Nordgren via GitGitGadget, Aug 20, 2026
  167. 5/8 history: validate squash revision rangesHarald Nordgren via GitGitGadget, Aug 20, 2026
  168. 6/8 history: protect branches when squashing a rangeHarald Nordgren via GitGitGadget, Aug 20, 2026
  169. 7/8 history: create squashed commits without editingHarald Nordgren via GitGitGadget, Aug 20, 2026
  170. Junio C HamanoAug 20, 2026
  171. Phillip WoodAug 24, 2026
  172. Junio C HamanoAug 24, 2026
  173. Phillip WoodAug 25, 2026
  174. Junio C HamanoAug 25, 2026
  175. 8/8 history: support editing squashed commit messagesHarald Nordgren via GitGitGadget, Aug 20, 2026
  176. 0/8 history: add squash subcommand to fold a rangeHarald Nordgren via GitGitGadget, Sep 8, 2026
  177. 1/8 history: extract helper for a commit's parent treeHarald Nordgren via GitGitGadget, Sep 8, 2026
  178. 2/8 history: give commit_tree_ext a message templateHarald Nordgren via GitGitGadget, Sep 8, 2026
  179. 3/8 sequencer: share the squash message marker helpers and flagsHarald Nordgren via GitGitGadget, Sep 8, 2026
  180. 4/8 history: add skeleton for squash subcommandHarald Nordgren via GitGitGadget, Sep 8, 2026
  181. Junio C HamanoSep 8, 2026
  182. 5/8 history: validate squash revision rangesHarald Nordgren via GitGitGadget, Sep 8, 2026
  183. 6/8 history: protect branches when squashing a rangeHarald Nordgren via GitGitGadget, Sep 8, 2026
  184. 8/8 history: support editing squashed commit messagesHarald Nordgren via GitGitGadget, Sep 8, 2026
  185. 7/8 history: create squashed commits without editingHarald Nordgren via GitGitGadget, Sep 8, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.