Martijn Braam
martijnbraam@fosstodon.org
Fun fact: Signed-off-by lines in git commit messages means sign the DCO of that project.
For authorship of the code there's already the From: field and putting a line you signed a document that doesn't exist for that project in your commit messages is legally whack.
1
0
0
@martijnbraam no, it doesn't? That's how git itself and the kernel use it, but even Git's own documentation is very clear that there is no global meaning and it is project-specific.
1
0
0
"The meaning of a signoff depends on the project to which you’re committing. For example, it may certify that the committer has the rights to submit the work under the project’s license or agrees to some contributor representation, such as a Developer Certificate of Origin. [...] Consult the documentation or leadership of the project to which you’re contributing to understand how the signoffs are used in that project.
https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---no-signoff
1
0
0
Martijn Braam
martijnbraam@fosstodon.org@HeNeArXn Doesn't change the fact that most projects _don't_ give any specification for signoffs so blanket adding them to all your commits still makes no sense whatsoever
2
0
0
@martijnbraam sure. Didn't know some people did that.
1
0
0
Pavel Machek
pavel
0
0
0