Thread (6 messages) flat view 6 messages, 4 authors, 2026-01-12

Re: [PATCH v10 0/3] status: show additional comparison with push branch when different from tracking branch

From: Junio C Hamano <hidden>
Date: 2026-01-01 23:09:46

"Harald Nordgren via GitGitGadget" [off-list ref] writes:
cc: Chris Torek chris.torek@gmail.com cc: Yee Cheng Chin
ychin.macvim@gmail.com cc: "brian m. carlson" sandals@crustytoothpaste.net
cc: Ben Knoble ben.knoble@gmail.com

Harald Nordgren (3):
  status: show comparison with configured goal branch
  improve tests
  use pushRemote and tracking branch
Again this seems to do a "step 1 goes in a direction, step 2 fixes
its mistake, step 3 changes course" drunken-man's walk.

The same advice to restructure them into a logical incremental
progression that moves the codebase in one consistent direction to
eventually reach the goal at the end applies.

I see you are now using pushremote_for_branch() that is already used
by branch_get_push().  If that gives us "the other thing" that we
would want to compare, instead of adding yet another configuration
variable users need to be aware of, that is really good.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help