- Joined
- Aug 7, 2013
- Messages
- 1,342
Hi,
So I've got a project under version control, and I make changes in bulk, partially because a lot of the code is intergrated with the rest, so changing one system/class can affect many other parts of the code.
Needless to say, making one change to overall code results in around ~100 differences between the version in the repo and the local version on my side.
All of these changes are meaningful, so I think for good documentation I should send commit messages with each change. What I've done is grouped some of the changes, which brings it to about ~30 commit messages every major update.
Is this normal? I've just found it tedious to write each commit message for each commit.
So I've got a project under version control, and I make changes in bulk, partially because a lot of the code is intergrated with the rest, so changing one system/class can affect many other parts of the code.
Needless to say, making one change to overall code results in around ~100 differences between the version in the repo and the local version on my side.
All of these changes are meaningful, so I think for good documentation I should send commit messages with each change. What I've done is grouped some of the changes, which brings it to about ~30 commit messages every major update.
Is this normal? I've just found it tedious to write each commit message for each commit.