Programming

3 readers

1 users here now

This magazine is dedicated to discussions on programming languages, software development, and coding. Whether you are a beginner programmer or an experienced developer, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as coding languages, software engineering, web development, and more. From the latest trends and frameworks to tips and tricks for debugging, this category covers a wide range of topics related to programming.

founded 2 years ago

git bisect and the importance of a clean history (danielrotter.at)

submitted 9 months ago by danrot@kbin.social to c/programming@kbin.social

4 comments fedilink hide all child comments

The value of a clean git history is often underestimated. I will explain one of the advantages based on the git bisect command.

you are viewing a single comment's thread
view the rest of the comments

[–] kevincox@lemmy.ml 0 points 9 months ago* (last edited 9 months ago) (1 children)

bisect stands for “binary search commit”

Haha, that is a funny misunderstanding. "bisect" stands for bisect. It is a word. It means to cut in half. Because the command cuts the range of suspicious commits into two, then tests which half the problem started in.

to divide into two usually equal parts

https://www.merriam-webster.com/dictionary/bisect

But I guess it can be misread as BInary SEarch CommiT.

[–] danrot@kbin.social 1 points 9 months ago

I swear, I didn't come up with that myself, I read that somewhere else, but of course I don't have a source anymore 🙈 Maybe some git developer is a huge fan of wordplays?