3 ms·
>> Commented-out code should not exist, granted .... I'll remove it later, I promise. > In my opinion, you should never commit commented out code. But the edi
by hibbelig 7y ago
>> Commented-out code should not exist, granted .... I'll remove it later, I promise.
> In my opinion, you should never commit commented out code.
But the editor works on uncommitted code, too. GP doesn't want to be distracted by that.
- gitgud 7y ago> ... so please don't distract me. I'll remove it later, I promise. It could mean people are literally looking over his shoulder at his screen and complaining. But to me, it implies that commented code is becoming part of the project source...
- gugagore 7y agoThanks to distributed version control, you can commit all sorts of trash in your own branch while figuring things out. These commits should not clutter the project source, though if you like hoarding data like I do, you might still preserve this history somewhere else in the repository.
- sacado2 7y agoNo, I'm talking about my own "private" code in my own editor. This is a conversation with my editor while I'm "in the zone". I (usually) don't commit commented-out code, for the reasons you mentioned above.
- gitgud 7y agoAh I see the context now, sorry for assuming the intent.