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

Re: [PATCH v11] status: show comparison with push remote tracking branch

From
PWPhillip Wood <phillip.wood123@gmail.com>
Date
Jan 2, 2026, 15:18 UTC
Message-ID
<6526c419-c60c-49d2-9c1a-52be7aca82f0@gmail.com>
In-Reply-To
<pull.2138.v11.git.git.1767352663477.gitgitgadget@gmail.com>
Hi Harald
On 02/01/2026 11:17, Harald Nordgren via GitGitGadget wrote:
Show 10 quoted lines
> From: Harald Nordgren <haraldnordgren@gmail.com>
> 
> "git status" on a branch that follows a remote branch compares
> commits on the current branch and the remote-tracking branch it
> builds upon, to show "ahead", "behind", or "diverged" status.
> 
> When working on a feature branch that tracks a remote feature branch,
> but you also want to track progress relative to the push remote's
> tracking branch (which may differ from the upstream branch), git status
> now shows an additional comparison.

This is great and it is really good that it is now using the default push destination rather than a custom config key.

Show 5 quoted lines
> When a push remote is configured (via branch.<name>.pushRemote or
> remote.pushDefault) git status shows both the comparison with the
> upstream tracking branch (as before) and an additional comparison with
> the push remote's tracking branch, if it differs from the upstream
> tracking branch.

Looking at the tests, it seems that the extra information is shown whenever the upstream branch differs from the default push destination even if they are on the same remote. I think that is sensible but this paragraph should be updated to reflect the fact that one does not need to set either of the "pushDefault" config settings to benefit from this.

Show 5 quoted lines
> The push branch comparison appears on a separate
> line after the upstream branch status, using the same format:
> - "Ahead of 'origin/feature' by N commits" when purely ahead
> - "Behind 'origin/feature' by N commits" when purely behind
> - "Diverged from 'origin/feature' by N commits" when diverged

I'm wondering why we don't reuse the existing messages - I don't see how using a different wording for the push destination compared to the upstream branch benefits the user. We should adjust the hints that are shown so that we only recommend pulling from the upstream branch and only recommend pushing to the default push destination but the comparisons should be the same. Also I don't find the message "Diverged from 'origin/feature' by N commits' very helpful, I'd find it more useful if it gave the ahead/behind count like we do for the upstream branch.

> Example output when tracking upstream/main with pushRemote set to origin:
>      On branch feature
>      Your branch is ahead of 'upstream/main' by 2 commits.
>        (use "git pull" if you want to integrate the remote branch with yours)

Is this a typo? - why are we recommending "git pull" when our branch is ahead of the upstream branch?

>      Ahead of 'origin/feature' by 5 commits.
It would be nice to have a hint suggesting the user runs "git push" here.
> The comparison is only shown when a push remote is configured and the
> push remote's tracking branch differs from the upstream tracking branch.

Looking at the tests, only the second half of that sentence appears to be true.

Show 24 quoted lines
> diff --git a/remote.c b/remote.c
> index 59b3715120..2317725f7d 100644
> --- a/remote.c
> +++ b/remote.c
> @@ -2237,6 +2237,81 @@ int stat_tracking_info(struct branch *branch, int *num_ours, int *num_theirs,
>   	return stat_branch_pair(branch->refname, base, num_ours, num_theirs, abf);
>   }
>   
> +static char *get_remote_push_branch(struct branch *branch, char **full_ref_out)
> +{
> +	const char *push_remote;
> +	const char *resolved;
> +	int flag;
> +	struct strbuf ref_buf = STRBUF_INIT;
> +	char *ret = NULL;
> +
> +	if (!branch)
> +		return NULL;
> +
> +	push_remote = pushremote_for_branch(branch, NULL);
> +	if (!push_remote)
> +		return NULL;
> +
> +	strbuf_addf(&ref_buf, "refs/remotes/%s/%s", push_remote, branch->name);

Shouldn't we be taking account of the push and fetch refspecs here? There is no guarantee that $branch maps to refs/remotes/$remote/$branch. To take a silly example, if we have

     remote.$remote.fetch = 
refs/heads/$branch:refs/remotes/$remote/abc-$branch
     remote.$remote.pull = refs/heads/$branch:refs/heads/xyz-$branch

Then we should be using "refs/remotes/$remote/abc-xyz-$branch" in the message above as "$branch" will be pushed to "xyz-$branch" on the remote which is fetched to "$remote/abc-xyz-$branch"

Show 6 quoted lines
> +
> +	resolved = refs_resolve_ref_unsafe(
> +		get_main_ref_store(the_repository),
> +		ref_buf.buf,
> +		RESOLVE_REF_READING,
> +		NULL, &flag);

As we don't use flag we can pass NULL - see the documentation for this function in refs.h

Show 15 quoted lines
> +static void format_push_branch_comparison(struct strbuf *sb,
> +					     const char *branch_refname,
> +					     const char *push_full,
> +					     const char *push_short,
> +					     enum ahead_behind_flags abf)
> +{
> +	int push_ahead = 0, push_behind = 0;
> +	int stat_result;
> +
> +	stat_result = stat_branch_pair(branch_refname, push_full,
> +				       &push_ahead, &push_behind, abf);
> +	if (stat_result < 0)
> +		return;
> +
> +	strbuf_addstr(sb, "\n");

As I said above it would be nice if we could use the existing messages here. Can we have a separate preparatory patch that refactors fromat_tracking_info() so that we can use the same messages for the upstream branch and the default push destination?

Show 6 quoted lines
> @@ -2311,6 +2387,19 @@ int format_tracking_info(struct branch *branch, struct strbuf *sb,
>   			strbuf_addstr(sb,
>   				_("  (use \"git pull\" if you want to integrate the remote branch with yours)\n"));
>   	}
> +
> +	if (!upstream_is_gone && sti >= 0 && abf != AHEAD_BEHIND_QUICK) {

Why do we handle AHEAD_BEHIND_QUICK differently to the upstream branch? Surely it would be useful to tell the user whether the branch is up to date with the default push destination or not?

Show 17 quoted lines
> diff --git a/t/t6040-tracking-info.sh b/t/t6040-tracking-info.sh
> index 0b719bbae6..f27ae719ad 100755
> --- a/t/t6040-tracking-info.sh
> +++ b/t/t6040-tracking-info.sh
> [...]
> +test_expect_success 'status shows ahead of both origin/main and feature branch' '
> +	(
> +		cd test &&
> +		git checkout -b feature2 origin/main &&
> +		git push origin HEAD &&
> +		advance work &&
> +		git status >../actual
> +	) &&
> +	cat >expect <<-EOF &&
> +	On branch feature2
> +	Your branch is ahead of ${SQ}origin/main${SQ} by 1 commit.
> +	  (use "git push" to publish your local commits)

Why are we still suggesting pushing to the upstream branch when we know the user is pushing to a different remote branch?

> +	Ahead of ${SQ}origin/feature2${SQ} by 1 commit.
Why aren't we suggesting to use "git push" here?

Thanks for working on this. With a few tweaks it will be a really useful improvement to "git status"

Phillip
Show 139 quoted lines
> +	nothing to commit, working tree clean
> +	EOF
> +	test_cmp expect actual
> +'
> +
> +test_expect_success 'checkout shows ahead of both origin/main and feature branch' '
> +	(
> +		cd test &&
> +		git checkout feature2 >../actual
> +	) &&
> +	cat >expect <<-EOF &&
> +	Your branch is ahead of ${SQ}origin/main${SQ} by 1 commit.
> +	  (use "git push" to publish your local commits)
> +
> +	Ahead of ${SQ}origin/feature2${SQ} by 1 commit.
> +	EOF
> +	test_cmp expect actual
> +'
> +
> +test_expect_success 'setup for ahead of tracked but diverged from main' '
> +	(
> +		cd test &&
> +		git checkout -b feature4 origin/main &&
> +		advance work1 &&
> +		git checkout origin/main &&
> +		advance work2 &&
> +		git push origin HEAD:main &&
> +		git checkout feature4 &&
> +		advance work3
> +	)
> +'
> +
> +test_expect_success 'status shows diverged from origin/main and ahead of feature branch' '
> +	(
> +		cd test &&
> +		git checkout feature4 &&
> +		git branch --set-upstream-to origin/main &&
> +		git push origin HEAD &&
> +		advance work &&
> +		git status >../actual
> +	) &&
> +	cat >expect <<-EOF &&
> +	On branch feature4
> +	Your branch and ${SQ}origin/main${SQ} have diverged,
> +	and have 3 and 1 different commits each, respectively.
> +	  (use "git pull" if you want to integrate the remote branch with yours)
> +
> +	Ahead of ${SQ}origin/feature4${SQ} by 1 commit.
> +
> +	nothing to commit, working tree clean
> +	EOF
> +	test_cmp expect actual
> +'
> +
> +test_expect_success 'setup upstream remote' '
> +	(
> +		cd test &&
> +		git remote add upstream ../. &&
> +		git fetch upstream &&
> +		git config remote.pushDefault origin
> +	)
> +'
> +
> +test_expect_success 'status with upstream remote and push.default set to origin' '
> +	(
> +		cd test &&
> +		git checkout -b feature5 upstream/main &&
> +		git push origin &&
> +		advance work &&
> +		git status >../actual
> +	) &&
> +	cat >expect <<-EOF &&
> +	On branch feature5
> +	Your branch is ahead of ${SQ}upstream/main${SQ} by 1 commit.
> +	  (use "git push" to publish your local commits)
> +
> +	Ahead of ${SQ}origin/feature5${SQ} by 1 commit.
> +
> +	nothing to commit, working tree clean
> +	EOF
> +	test_cmp expect actual
> +'
> +
> +test_expect_success 'status with upstream remote and push.default set to origin and diverged' '
> +	(
> +		cd test &&
> +		git checkout -b feature6 upstream/main &&
> +		advance work &&
> +		git push origin &&
> +		git reset --hard upstream/main &&
> +		advance work &&
> +		git status >../actual
> +	) &&
> +	cat >expect <<-EOF &&
> +	On branch feature6
> +	Your branch is ahead of ${SQ}upstream/main${SQ} by 1 commit.
> +	  (use "git push" to publish your local commits)
> +
> +	Diverged from ${SQ}origin/feature6${SQ} by 2 commits.
> +
> +	nothing to commit, working tree clean
> +	EOF
> +	test_cmp expect actual
> +'
> +
> +test_expect_success 'status with upstream remote and push branch up to date' '
> +	(
> +		cd test &&
> +		git checkout -b feature7 upstream/main &&
> +		git push origin &&
> +		git status >../actual
> +	) &&
> +	cat >expect <<-EOF &&
> +	On branch feature7
> +	Your branch is up to date with ${SQ}upstream/main${SQ}.
> +
> +	Your branch is up to date with ${SQ}origin/feature7${SQ}.
> +
> +	nothing to commit, working tree clean
> +	EOF
> +	test_cmp expect actual
> +'
> +
> +test_expect_success 'checkout shows push branch up to date' '
> +	(
> +		cd test &&
> +		git checkout feature7 >../actual
> +	) &&
> +	cat >expect <<-EOF &&
> +	Your branch is up to date with ${SQ}upstream/main${SQ}.
> +
> +	Your branch is up to date with ${SQ}origin/feature7${SQ}.
> +	EOF
> +	test_cmp expect actual
> +'
> +
>   test_done
> 
> base-commit: 68cb7f9e92a5d8e9824f5b52ac3d0a9d8f653dbe
Previous: Harald Nordgren via GitGitGadgetNext: Harald Nordgren
Message 72 of 259 in “status: show default branch comparison when tracking non-default branch”
  1. status: show default branch comparison when tracking non-default branchHarald Nordgren via GitGitGadget, Dec 23, 2025
  2. Junio C HamanoDec 23, 2025
  3. Harald NordgrenDec 23, 2025
  4. Harald NordgrenDec 23, 2025
  5. Chris TorekDec 23, 2025
  6. Harald NordgrenDec 23, 2025
  7. Chris TorekDec 23, 2025
  8. Another look?Harald Nordgren, Jan 1, 2026
  9. Junio C HamanoDec 23, 2025
  10. Harald NordgrenDec 23, 2025
  11. 0/2 status: show default branch comparison when tracking non-default branchHarald Nordgren via GitGitGadget, Dec 23, 2025
  12. 1/2 status: show comparison with upstream default branchHarald Nordgren via GitGitGadget, Dec 23, 2025
  13. brian m. carlsonDec 24, 2025
  14. Junio C HamanoDec 24, 2025
  15. Another look?Harald Nordgren, Jan 1, 2026
  16. 2/2 Simplify default branch comparison logicHarald Nordgren via GitGitGadget, Dec 23, 2025
  17. Harald NordgrenDec 24, 2025
  18. 0/3 status: show default branch comparison when tracking non-default branchHarald Nordgren via GitGitGadget, Dec 24, 2025
  19. 1/3 status: show comparison with upstream default branchHarald Nordgren via GitGitGadget, Dec 24, 2025
  20. 2/3 Simplify default branch comparison logicHarald Nordgren via GitGitGadget, Dec 24, 2025
  21. 3/3 Use repo.settings.statusGoalBranch config for status comparisonHarald Nordgren via GitGitGadget, Dec 24, 2025
  22. 0/4 status: show default branch comparison when tracking non-default branchHarald Nordgren via GitGitGadget, Dec 24, 2025
  23. 1/4 status: show comparison with upstream default branchHarald Nordgren via GitGitGadget, Dec 24, 2025
  24. 2/4 Simplify default branch comparison logicHarald Nordgren via GitGitGadget, Dec 24, 2025
  25. 3/4 Use repo.settings.statusGoalBranch config for status comparisonHarald Nordgren via GitGitGadget, Dec 24, 2025
  26. 4/4 Rename default_remote to goal_branchHarald Nordgren via GitGitGadget, Dec 24, 2025
  27. 0/5 status: show default branch comparison when tracking non-default branchHarald Nordgren via GitGitGadget, Dec 24, 2025
  28. 1/5 status: show comparison with upstream default branchHarald Nordgren via GitGitGadget, Dec 24, 2025
  29. 2/5 Simplify default branch comparison logicHarald Nordgren via GitGitGadget, Dec 24, 2025
  30. 3/5 Use repo.settings.statusGoalBranch config for status comparisonHarald Nordgren via GitGitGadget, Dec 24, 2025
  31. 4/5 Rename default_remote to goal_branchHarald Nordgren via GitGitGadget, Dec 24, 2025
  32. 5/5 Add warning for malformed statusGoalBranch configHarald Nordgren via GitGitGadget, Dec 24, 2025
  33. 0/6 status: show default branch comparison when tracking non-default branchHarald Nordgren via GitGitGadget, Dec 24, 2025
  34. 1/6 status: show comparison with upstream default branchHarald Nordgren via GitGitGadget, Dec 24, 2025
  35. 2/6 Simplify default branch comparison logicHarald Nordgren via GitGitGadget, Dec 24, 2025
  36. 3/6 Use repo.settings.statusGoalBranch config for status comparisonHarald Nordgren via GitGitGadget, Dec 24, 2025
  37. 4/6 Rename default_remote to goal_branchHarald Nordgren via GitGitGadget, Dec 24, 2025
  38. 5/6 Add warning for malformed statusGoalBranch configHarald Nordgren via GitGitGadget, Dec 24, 2025
  39. 6/6 Change config key to status.compareBranchHarald Nordgren via GitGitGadget, Dec 24, 2025
  40. Junio C HamanoDec 25, 2025
  41. Harald NordgrenDec 25, 2025
  42. Junio C HamanoDec 26, 2025
  43. Harald NordgrenDec 26, 2025
  44. status: additional comparison with goal branchHarald Nordgren via GitGitGadget, Dec 25, 2025
  45. status: show comparison with configured goal branchHarald Nordgren via GitGitGadget, Dec 25, 2025
  46. Code review?Harald Nordgren, Dec 28, 2025
  47. Junio C HamanoDec 28, 2025
  48. Code review?Harald Nordgren, Dec 28, 2025
  49. Ben KnobleDec 28, 2025
  50. Triangular workflowsHarald Nordgren, Dec 29, 2025
  51. Harald NordgrenJan 1, 2026
  52. Harald NordgrenDec 30, 2025
  53. Junio C HamanoDec 28, 2025
  54. Code review?Harald Nordgren, Dec 28, 2025
  55. 0/2 status: show comparison with configured goal branchHarald Nordgren via GitGitGadget, Dec 28, 2025
  56. 1/2 status: show comparison with configured goal branchHarald Nordgren via GitGitGadget, Dec 28, 2025
  57. 2/2 improve testsHarald Nordgren via GitGitGadget, Dec 28, 2025
  58. 0/3 status: show additional comparison with push branch when different from tracking branchHarald Nordgren via GitGitGadget, Dec 30, 2025
  59. 1/3 status: show comparison with configured goal branchHarald Nordgren via GitGitGadget, Dec 30, 2025
  60. 2/3 improve testsHarald Nordgren via GitGitGadget, Dec 30, 2025
  61. 3/3 use pushRemote and tracking branchHarald Nordgren via GitGitGadget, Dec 30, 2025
  62. Junio C HamanoJan 1, 2026
  63. Another look?Harald Nordgren, Jan 1, 2026
  64. Kristoffer HaugsbakkJan 2, 2026
  65. Another look?Harald Nordgren, Jan 2, 2026
  66. Kristoffer HaugsbakkJan 12, 2026
  67. Junio C HamanoJan 4, 2026
  68. Nico WilliamsJan 4, 2026
  69. Junio C HamanoJan 4, 2026
  70. D. Ben KnobleJan 5, 2026
  71. status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 2, 2026
  72. Phillip WoodJan 2, 2026
  73. Another look?Harald Nordgren, Jan 2, 2026
  74. Phillip WoodJan 3, 2026
  75. Another look?Harald Nordgren, Jan 3, 2026
  76. 0/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 2, 2026
  77. 1/2 refactor: format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 2, 2026
  78. 2/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 2, 2026
  79. 0/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 3, 2026
  80. 1/2 refactor: format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 3, 2026
  81. 2/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 3, 2026
  82. 0/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 3, 2026
  83. 1/2 refactor: format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 3, 2026
  84. Junio C HamanoJan 4, 2026
  85. Another look?Harald Nordgren, Jan 4, 2026
  86. Another look?Harald Nordgren, Jan 4, 2026
  87. Junio C HamanoJan 5, 2026
  88. 2/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 3, 2026
  89. 0/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 4, 2026
  90. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 4, 2026
  91. 2/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 4, 2026
  92. 0/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 4, 2026
  93. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 4, 2026
  94. Junio C HamanoJan 5, 2026
  95. Another look?Harald Nordgren, Jan 5, 2026
  96. Another look?Harald Nordgren, Jan 5, 2026
  97. Junio C HamanoJan 5, 2026
  98. Another look?Harald Nordgren, Jan 5, 2026
  99. Junio C HamanoJan 5, 2026
  100. ABQHarald Nordgren, Jan 6, 2026
  101. ABQHarald Nordgren, Jan 8, 2026
  102. 2/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 4, 2026
  103. 0/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 5, 2026
  104. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 5, 2026
  105. Phillip WoodJan 9, 2026
  106. Harald NordgrenJan 9, 2026
  107. 2/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 5, 2026
  108. Phillip WoodJan 9, 2026
  109. Harald NordgrenJan 9, 2026
  110. Ben KnobleJan 9, 2026
  111. Patrick SteinhardtJan 9, 2026
  112. Harald NordgrenJan 9, 2026
  113. Phillip WoodJan 12, 2026
  114. Harald NordgrenJan 12, 2026
  115. Phillip WoodJan 13, 2026
  116. Harald NordgrenJan 13, 2026
  117. 0/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 9, 2026
  118. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 9, 2026
  119. 2/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 9, 2026
  120. 0/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 9, 2026
  121. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 9, 2026
  122. Junio C HamanoJan 10, 2026
  123. 2/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 9, 2026
  124. Junio C HamanoJan 10, 2026
  125. Harald NordgrenJan 10, 2026
  126. Junio C HamanoJan 10, 2026
  127. Junio C HamanoJan 10, 2026
  128. Harald NordgrenJan 10, 2026
  129. Harald NordgrenJan 10, 2026
  130. Junio C HamanoJan 10, 2026
  131. Harald NordgrenJan 10, 2026
  132. Junio C HamanoJan 11, 2026
  133. 0/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 10, 2026
  134. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 10, 2026
  135. 2/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 10, 2026
  136. 0/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 10, 2026
  137. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 10, 2026
  138. 2/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 10, 2026
  139. 0/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 10, 2026
  140. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 10, 2026
  141. 2/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 10, 2026
  142. 0/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 12, 2026
  143. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 12, 2026
  144. 2/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 12, 2026
  145. Junio C HamanoJan 12, 2026
  146. Harald NordgrenJan 13, 2026
  147. 0/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 13, 2026
  148. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 13, 2026
  149. 2/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 13, 2026
  150. 0/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 13, 2026
  151. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 13, 2026
  152. 2/2 status: show comparison with push remote tracking branchHarald Nordgren via GitGitGadget, Jan 13, 2026
  153. Jeff KingJan 13, 2026
  154. Triangular workflowHarald Nordgren, Jan 13, 2026
  155. Jeff KingJan 13, 2026
  156. Triangular workflowHarald Nordgren, Jan 13, 2026
  157. D. Ben KnobleJan 14, 2026
  158. Triangular workflowHarald Nordgren, Jan 14, 2026
  159. Ben KnobleJan 14, 2026
  160. Jeff KingJan 14, 2026
  161. Triangular workflowHarald Nordgren, Jan 14, 2026
  162. Jeff KingJan 14, 2026
  163. Triangular workflowHarald Nordgren, Jan 14, 2026
  164. Jeff KingJan 14, 2026
  165. Ben KnobleJan 14, 2026
  166. Jeff KingJan 14, 2026
  167. D. Ben KnobleJan 15, 2026
  168. Junio C HamanoJan 14, 2026
  169. Junio C HamanoJan 14, 2026
  170. Jeff KingJan 14, 2026
  171. Ben KnobleJan 14, 2026
  172. Triangular workflowHarald Nordgren, Jan 14, 2026
  173. Chris TorekJan 19, 2026
  174. Triangular workflowHarald Nordgren, Jan 20, 2026
  175. Triangular workflowHarald Nordgren, Jan 14, 2026
  176. Junio C HamanoJan 14, 2026
  177. Triangular workflowHarald Nordgren, Jan 18, 2026
  178. Phillip WoodJan 15, 2026
  179. Junio C HamanoJan 15, 2026
  180. Jeff KingJan 15, 2026
  181. 0/2 status: add status.compareBranches config for multiple branch comparisonsHarald Nordgren via GitGitGadget, Jan 18, 2026
  182. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 18, 2026
  183. 2/2 status: add status.compareBranches config for multiple branch comparisonsHarald Nordgren via GitGitGadget, Jan 18, 2026
  184. Jeff KingJan 19, 2026
  185. Memory leakHarald Nordgren, Jan 20, 2026
  186. Memory leakHarald Nordgren, Jan 20, 2026
  187. Junio C HamanoJan 20, 2026
  188. Junio C HamanoJan 21, 2026
  189. Jeff KingJan 21, 2026
  190. Memory leakHarald Nordgren, Jan 22, 2026
  191. Junio C HamanoJan 22, 2026
  192. 0/2 status: add status.compareBranches config for multiple branch comparisonsHarald Nordgren via GitGitGadget, Jan 22, 2026
  193. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 22, 2026
  194. 2/2 status: add status.compareBranches config for multiple branch comparisonsHarald Nordgren via GitGitGadget, Jan 22, 2026
  195. Jeff KingJan 22, 2026
  196. Harald NordgrenJan 22, 2026
  197. Junio C HamanoJan 22, 2026
  198. Junio C HamanoJan 22, 2026
  199. Harald NordgrenJan 22, 2026
  200. Junio C HamanoJan 22, 2026
  201. Junio C HamanoJan 22, 2026
  202. Jeff KingJan 22, 2026
  203. Jeff KingJan 22, 2026
  204. Jeff KingJan 22, 2026
  205. Harald NordgrenJan 24, 2026
  206. Junio C HamanoJan 25, 2026
  207. Harald NordgrenFeb 8, 2026
  208. Junio C HamanoJan 22, 2026
  209. Junio C HamanoJan 22, 2026
  210. Harald NordgrenJan 22, 2026
  211. Junio C HamanoJan 22, 2026
  212. Harald NordgrenJan 22, 2026
  213. 0/2 status: add status.compareBranches config for multiple branch comparisonsHarald Nordgren via GitGitGadget, Jan 22, 2026
  214. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Jan 22, 2026
  215. 2/2 status: add status.compareBranches config for multiple branch comparisonsHarald Nordgren via GitGitGadget, Jan 22, 2026
  216. Harald NordgrenFeb 21, 2026
  217. Junio C HamanoFeb 21, 2026
  218. D. Ben KnobleFeb 22, 2026
  219. Jeff KingFeb 23, 2026
  220. Harald NordgrenFeb 24, 2026
  221. Junio C HamanoFeb 24, 2026
  222. Harald NordgrenFeb 25, 2026
  223. Junio C HamanoFeb 25, 2026
  224. Jeff KingFeb 25, 2026
  225. Junio C HamanoFeb 25, 2026
  226. Harald NordgrenFeb 26, 2026
  227. D. Ben KnobleFeb 25, 2026
  228. 0/2 status: add status.compareBranches config for multiple branch comparisonsHarald Nordgren via GitGitGadget, Feb 25, 2026
  229. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Feb 25, 2026
  230. 2/2 status: add status.compareBranches config for multiple branch comparisonsHarald Nordgren via GitGitGadget, Feb 25, 2026
  231. Junio C HamanoFeb 25, 2026
  232. Harald NordgrenFeb 26, 2026
  233. 0/2 status: add status.compareBranches config for multiple branch comparisonsHarald Nordgren via GitGitGadget, Feb 26, 2026
  234. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Feb 26, 2026
  235. 2/2 status: add status.compareBranches config for multiple branch comparisonsHarald Nordgren via GitGitGadget, Feb 26, 2026
  236. Junio C HamanoMar 2, 2026
  237. Harald NordgrenMar 4, 2026
  238. Junio C HamanoFeb 26, 2026
  239. Harald NordgrenMar 1, 2026
  240. Kristoffer HaugsbakkMar 1, 2026
  241. Junio C HamanoMar 2, 2026
  242. 0/2 status: add status.compareBranches config for multiple branch comparisonsHarald Nordgren via GitGitGadget, Mar 4, 2026
  243. 1/2 refactor format_branch_comparison in preparationHarald Nordgren via GitGitGadget, Mar 4, 2026
  244. 2/2 status: add status.compareBranches config for multiple branch comparisonsHarald Nordgren via GitGitGadget, Mar 4, 2026
  245. Junio C HamanoMar 4, 2026
  246. Harald NordgrenMar 9, 2026
  247. Junio C HamanoMar 9, 2026
  248. Junio C HamanoJan 10, 2026
  249. Harald NordgrenJan 10, 2026
  250. Kristoffer HaugsbakkJan 12, 2026
  251. Yee Cheng ChinDec 23, 2025
  252. Harald NordgrenDec 23, 2025
  253. Yee Cheng ChinDec 24, 2025
  254. Junio C HamanoDec 24, 2025
  255. Yee Cheng ChinDec 24, 2025
  256. Junio C HamanoDec 24, 2025
  257. Harald NordgrenDec 24, 2025
  258. Another look?Harald Nordgren, Jan 1, 2026
  259. Harald NordgrenDec 24, 2025

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.