Git bisect (2006) • Hacker News Board

Re: Git bisect (2006)

#11

Post by lmm » Thu, Aug 18, 2016, 11:21 AM UTC

pwfisher wrote: post #4

This is a revealing peek at the complexity of merged history. You can't project a "git space" onto a line, so a (linear) listing of commits just misleads you into thinking that your history is linear. That complexity is why I always prefer to rebase and keep my history an actual straight line. TL;DR - Merging is powerful, but comes with a cost. - Rebase is your friend. Keep it simple.

Bisecting with commits that weren't actually tested because no-one ever checked out a tree that literally looked like that is worse, IME. I'd rather embrace the fact that the commits I have to work with are what Bob had on his workstation on Tuesday and what Jim had on his workstation on Tuesday than try to bisect using a "fictional" commit that's actually "what Jim had on Tuesday + Bob's changes up to Friday".

Re: Git bisect (2006)

#12

Post by Noseshine » Thu, Aug 18, 2016, 11:24 AM UTC

randomanybody wrote: post #2

"To visualise this, it’s simplest to think of the state of your repository as a point in a high-dimensional ‘code-space’, in which branches are represented as n-dimensional membranes, mapping the spatial loci of successive commits onto the projected manifold of each cloned repository." http://tartley.com/?p=1267

That's really... good. I have the theory that whether or not you see this is as an attempt at a legitimate explanation or just a joke depends on your level of self-confidence. I think few people will actually understand it (if they do it's a miracle, since such understanding would be a product purely of your own mind trying to interpret sense into what it sees), but those who lack self-confidence will see the fault in themselves, while those with enough confidence upon realizing they don't understand it will realize it's a joke, because if it wasn't they should have understood it.

Of course, now I'm open to a reply that demonstrates that it isn't a joke but makes perfect sense and that I'm clueless and overconfident... :)

Re: Git bisect (2006)

#13

Post by ZeroGravitas » Thu, Aug 18, 2016, 11:29 AM UTC

Noseshine wrote: post #12

randomanybody wrote: post #2

"To visualise this, it’s simplest to think of the state of your repository as a point in a high-dimensional ‘code-space’, in which branches are represented as n-dimensional membranes, mapping the spatial loci of successive commits onto the projected manifold of each cloned repository." http://tartley.com/?p=1267

That's really... good. I have the theory that whether or not you see this is as an attempt at a legitimate explanation or just a joke depends on your level of self-confidence. I think few people will actually understand it (if they do it's a miracle, since such understanding would be a product purely of your own mind trying to interpret sense into what it sees), but those who lack self-confidence will see the fault i…