Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

"Why doesn't git bisect work?"

"well, it landed on this rebased commit that's huge. I guess it was a kind of useful, just not as useful as we'd like".



Haha, true! On the other hand, is that better or worse than running into a string of "wip" commits that had the code in a broken state.


But if the alternative is that it's ten commits and most of them don't work anyway, the bisect takes longer to give you the same lousy information.


That's not the alternative, who develops like that?

It's like the first time I saw the essay calling ORM's the "vietnam of the software industry". I remember reading it and wondering who the hell would use ORM's in that manner?

Apparently a lot of people, but if you're using rebase because you don't know how to create commits that build and are functional then I submit the issue is with you.


> That's not the alternative, who develops like that?

As an independent contractor working with many different companies, unfortunately, virtually everybody.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: