Page MenuHomeFreeBSD

tools: git hooks: drop "submitted by" from commit template
ClosedPublic

Authored by kevans on Jan 9 2021, 7:55 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mar 7 2024, 12:43 PM
Unknown Object (File)
Feb 11 2024, 6:12 PM
Unknown Object (File)
Dec 22 2023, 10:48 PM
Unknown Object (File)
Dec 20 2023, 6:20 PM
Unknown Object (File)
Oct 28 2023, 2:41 AM
Unknown Object (File)
Oct 23 2023, 2:49 AM
Unknown Object (File)
Jul 28 2023, 7:45 PM
Unknown Object (File)
Jun 28 2023, 8:35 PM
Subscribers
None

Details

Reviewers
emaste
imp
Summary

With the switch to git, we should strive to properly attribute every
commit appropriately with the metadata that's provided to do so. In this
case, the submitter should be recorded via the author metadata. Committing
an arbitrary patch, one can set it as such:

git commit --author="John Smith <smith@example.com>"

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 36067
Build 32956: arc lint + arc unit

Event Timeline

kevans requested review of this revision.Jan 9 2021, 7:55 PM
kevans created this revision.

perhaps we should include git commit --author in the template, something like "should be set appropriately, using git commit --author... if someone"?

perhaps we should include git commit --author in the template, something like "should be set appropriately, using git commit --author... if someone"?

Yes. this is an obscure edge case for git usage for most people....

Explicitly reference git commit --author

tools/tools/git/hooks/prepare-commit-msg
60

why the \ quotes on the single back-tick quotes? Why not single, forward ticks?

tools/tools/git/hooks/prepare-commit-msg
60

I'm indifferent, just used to styling commands with backticks which aren't directly usable without escape in this context. No objection to using some other stylization.

tools/tools/git/hooks/prepare-commit-msg
60

I've become comfortable with backticks for commands via markdown and they seem fine in plain text too.

tools/tools/git/hooks/prepare-commit-msg
60

So... change it, or leave it?

tools/tools/git/hooks/prepare-commit-msg
60

I'd leave it as you have it now

This revision is now accepted and ready to land.Jan 11 2021, 9:31 PM