-
rsync
An open source utility that provides fast incremental file transfer. It also has useful features for backup and restore operations among many other use cases.
-
Git
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
The commit descriptions on this project are atrocious:
https://github.com/WayneD/rsync/commits/master
"A few more minor tweaks."
"A few more minor changes."
"Some extra file-list safety checks."
Those are full commit messages. No why. No how. Just a very terse, and typically generic "what."
By way of comparison, here's what commits to git itself look like:
https://github.com/git/git/commit/198551ca54f6ff1c95c9357ccc...
https://github.com/git/git/commit/dee8a1455c8ad443ef59e0d5b7...
Each commit contains paragraphs of explanatory material.
https://github.com/git/git/commits/master
Please folks, I beg of you, spend time writing your commit messages. You're not writing them for you, today. You're writing them for others, including your future self. Also, a PR description is not a suitable substitute for good commit messages for multiple reasons:
1. If the PR is a single commit, then it's just the commit message and your job is probably done.
2. If there are multiple commits, then the PR should summarize what all the commits do in total.
3. The PR description is typically written hours or days after the commit(s). What was fresh in your head when you wrote that code is now stale and you will struggle to recall why you made a change in a particular way more than if you wrote it down fresh when you commit the change.
4. The PR description is not part of the repo's history. It requires access to a (typically propriety) platform to read.
The commit descriptions on this project are atrocious:
https://github.com/WayneD/rsync/commits/master
"A few more minor tweaks."
"A few more minor changes."
"Some extra file-list safety checks."
Those are full commit messages. No why. No how. Just a very terse, and typically generic "what."
By way of comparison, here's what commits to git itself look like:
https://github.com/git/git/commit/198551ca54f6ff1c95c9357ccc...
https://github.com/git/git/commit/dee8a1455c8ad443ef59e0d5b7...
Each commit contains paragraphs of explanatory material.
https://github.com/git/git/commits/master
Please folks, I beg of you, spend time writing your commit messages. You're not writing them for you, today. You're writing them for others, including your future self. Also, a PR description is not a suitable substitute for good commit messages for multiple reasons:
1. If the PR is a single commit, then it's just the commit message and your job is probably done.
2. If there are multiple commits, then the PR should summarize what all the commits do in total.
3. The PR description is typically written hours or days after the commit(s). What was fresh in your head when you wrote that code is now stale and you will struggle to recall why you made a change in a particular way more than if you wrote it down fresh when you commit the change.
4. The PR description is not part of the repo's history. It requires access to a (typically propriety) platform to read.