docs(mounts): Correct fs-freq reference to fs_freq
Corrects the spelling of the fstab 'fs_freq' field from 'fs-freq' to 'fs_freq' in documentation, examples, and comments.
Closes #GH-6210
Proposed Commit Message
docs(mounts): Correct fs-freq reference to fs_freq (#6262)
Corrects the spelling of the fstab 'fs_freq' field from 'fs-freq'
to 'fs_freq' in documentation, examples, and comments.
Fixes GH-6210
Additional Context
Test Steps
Merge type
- [x] Squash merge using "Proposed Commit Message"
- [ ] Rebase and merge unique commits. Requires commit messages per-commit each referencing the pull request number (#<PR_NUM>)
@ibrahim-mojalled thank you much for improving cloud-init. I confirm this is the correct fix and we would like to include it in upstream cloud-init. To allow us to use your changset, would you please sign this project's contributor license agreement at https://ubuntu.com/legal/contributors? Once the cla-check passes, we can merge your changeset.
Many thanks!
Also in the commit message footer we typically use the format to allow our tooling to best represent release fixes using a project-standard convention:
Fixes GH-6210
We can fix your commit message upon merge if you like, the only thing we'd need though is that CLA signed at the link above.
@blackboxsw I signed the CLA before and I rechecked through the link you provided and it shows that "The provided email address is already associated with a CLA".
LGTM, thanks.
But the CLA seems to be not signed by: https://github.com/canonical/cloud-init/actions/runs/15607390546/job/45054285701#step:2:10.
Are you, @ibrahim-mojalled, sure that you have signed it with the email [email protected]?
@aciba90 I updated the git config email address, the problem should be fixed now hopefully.