4 ms·
It's a shame the fork doesn't use better commit messages than they do. For example, "Fixes" is the entire commit message for https://github.com/temporary-audac
by 0x0 5y ago
It's a shame the fork doesn't use better commit messages than they do.
For example, "Fixes" is the entire commit message for https://github.com/temporary-audacity/audacity/commit/d9f30b2b729becf7f3810b32c5b55f3886687e63 https://github.com/temporary-audacity/audacity/commit/d9f30b...
Commit messages like these do not inspire a lot of confidence. It would be a lot better (and easier to compare the original and the fork) if the commit message was something like "[Remove-Tracking] Remove SentryHelper.h and sentry ADD_EXCEPTION_CONTEXT usage"
- moron4hire 5y ago> Commit messages like these do not inspire a lot of confidence It's really not that big of a deal. When it comes to this sort of thing, the important thing is that the tracking code is actually and fully removed. There is no way to tell that from a commit message. The commit message could be written as you suggest and it could be a lie. With a either good commit message or poor, the code still needs to be verified.
- chris_j 5y agoA commit message should ideally describe the intent of the commit. You can read the diff to discover how it was accomplished. They serve different purposes.