Add git commit --amend with a comment about doing a final check of the commit
message before the push. Update with some more specific guidance on a good
commit message. Add link to commit message section. Minor tweaks I noticed
while doing this as well for having one setence one line.
Submitted by cy@
% git commit --amend # one last sanity check on commit message
% git push freebsd
% git push freebsd
....
....
Here 'good' means:
Here 'good' means:
. All the right files, and none of the wrong ones, were merged into contrib/glorbnitz.
. All the right files, and none of the wrong ones, were merged into contrib/glorbnitz.
. No other changes are in the tree
. No other changes are in the tree.
. The commit messages look good.
. The commit messages look <<commit-log-message,good>>. It should contain a summary of what's changed since the last merge to the FreeBSD main line and any caveats.
. UPDATING should be updated if there is anything of note, such as user visible changes, important upgrade concerns, etc.
[NOTE]
[NOTE]
====
====
This hasn't connected `glorbnitz` to the build yet. How so do that is specific to the software being imported.
This hasn't connected `glorbnitz` to the build yet.
How so do that is specific to the software being imported and is beyond the scope of this tutorial.