3 ms·
; THIS IS REMOVED BECAUSE IT KILLS FILES OPENED FOR ; MAIL-MERGE. I DON'T KNOW RIGHT NOW WHY THIS IS HERE Ah, a classic from before the days of source con
by aetherspawn 4y ago
; THIS IS REMOVED BECAUSE IT KILLS FILES OPENED FOR
; MAIL-MERGE. I DON'T KNOW RIGHT NOW WHY THIS IS HERE
Ah, a classic from before the days of source control.
- wk_end 4y agoI see stuff like this in source controlled repos all the time! The argument is that, even if it's in the git history, it'll get lost/forgotten about in case it's ever needed again.
- flohofwoe 4y agoIn some(!) cases it totally makes sense to provide a hint for the person who might read the source code and wonder why there is a certain 'void' recognisable in the code, because it has been designed around another piece of code or data that is no longer there. Better to keep a short comment in the source file for readers to stumble over, and then via blame it's easy to read up on the whole history in version control.