Re: [PATCH v14 2/2] checkout: extend --track with a "fetch" mode to refresh start-point

From: Harald Nordgren <haraldnordgren@gmail.com>
Date: Jun 25, 2026, 08:53 UTC
Message-ID: <CAHwyqnWdsYGHMcMT=B-Vdrb_DUK61QBs0-YvWkdeq958v_r35w@mail.gmail.com>
In-Reply-To: <43C04FB5-7FE5-4535-A79A-C35449EB38C0@gmail.com>

Hi!

I think you are touching on the critical point here; Git is likely one of the most ordered software projects that exist (I haven't worked on Linux kernel but that's the only one I can imagine is more stringent), and every "real job" I had has been fast-paced and chaotic.

I believe that we must leave the ivory tower and make Git great for the real world.

> I also fetch several times a day to keep up to date locally

I think this is also something that makes you not feel the pain as much. As a technical leader who spends time on reviewing, it gives a more of a aloof/holistic view. And more likely to have already fetched the latest master at any given point. When I worked as an IC, I forked from a stale branch 1000's of times and often felt that pain, I would have wished for this feature.

> So « bad workflow » I agree with, but am plenty guilty of :)

Is it "bad", or is it just a completely normal workflow for 99% of developers? Maybe we should cater to the normal workflow rather than chastising them.

> To wrap up, I wonder if the convenience of this proposal is especially aimed at folks like my corporate environment (where « build near the tip and integrate quickly » is the norm), but less than useful for those same folks in a different situation?

Sure, we can say that, but that's likely 99% of all Git users?

Harald

Harald