3 ms·
> realistically nobody is going to do that, because it's pretty inefficient way to spend your time. Of course you do! And it's not am inefficient use of your t
by bonzini 8y ago
> realistically nobody is going to do that, because it's pretty inefficient way to spend your time.
Of course you do! And it's not am inefficient use of your time, because it helps reviewers now, and yourself when you're bisecting later.
> And even then, you're still removing context (unless you're just fixing a typo).
You place that context in the commit message.
- fulafel 8y agoIME this is a very rare level of sophistication in use of rebase. And how do you detect that you forgot / was too busy to do it, when you go back 6 months later? It's fragile, "fail-open".
- bonzini 8y agoYou would be surprised. For example, this is a guide my colleague wrote to describe his git workflow: https://github.com/tianocore/tianocore.github.io/wiki/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers https://github.com/tianocore/tianocore.github.io/wiki/Laszlo...