Re:Git is my buddy: Effective Git as a solo developer
by account42 on Wednesday February 24, 2021 @04:38AM
(#26248251)
Basically, you want to keep the history of individual logical patches to the codebase, but not the meta-history of how those patches were made.
[ Parent
| on HN ]
Re:Git is my buddy: Effective Git as a solo developer
by xorcist on Wednesday February 24, 2021 @05:17AM
(#26248459)
It helps to think about how git grew out of an email based workflow.
A commit is essentially an email. It has a sender, date, a subject line and a message body. The commit message format is subject, empty line, body. Think of git repository as an archived mailing list worth of patches.
Much the same as you wouldn't send an email describing several days of work without proofreading it, you should treat your commits the same way. The git design grew out of this usage, which was much harder in something like Subversion.
No one would send an email to the kernel mailing list suggesting a patch set that included errors, false starts, and reverts. That would waste reviewers' time. Code history is a craft to aid understading the code, it is not an undo log.