Highlights from Git 2.35

Re:Highlights from Git 2.35 by Hackbraten on Tuesday January 25, 2022 @04:31PM (#30078372)

> I specifically want more points to bisect against (yes, I'm one of those who actually uses bisect).

Wouldn’t that make bisecting more difficult?

If your history is full of checkpoint commits, wouldn’t bisect send you to broken commits (that you’d have to `--skip`) more often?

Why would you want to deal with those extra steps?

[ Parent | on HN ]

Re:Highlights from Git 2.35 by skinkestek on Tuesday January 25, 2022 @05:32PM (#30079048)

Just make sure every step make sense. One or even two or three extra bisect steps is nothing in my kind of projects as long as you get a very specific change.

I guess on AAA game engines where compiles take half an hour it is more of a problem but in my case it takes 30 - 120 seconds depending on project.

(I do have uncompilable WIP steps, and those I am kind of ashamed for but those are so few and so far between that it doesn't matter.)

[ Parent | on HN ]