You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The log of the commit should contain some basic information which can help one user to understand the content of the binary file.
My proposal, open for discussion, is the following.
first row of the log contains the board name and fw version, so that one can see most important info first.
in some rows below write info about when the built was done and the SHA of the used repositories. that may be useful to re-create the binary from source code.
finally add a comment about the differences in functionalities with the previously committed fw version.
I suggest to also include a blank line between the first row of the commit message and remaining rows, so that some git-related tools can properly work. See http://chris.beams.io/posts/git-commit/#separate .
The log of the commit should contain some basic information which can help one user to understand the content of the binary file.
My proposal, open for discussion, is the following.
An example is in SHA: 4b0356a
if we all follow some rule of the sort, the repository will be more clear.
The issue can interest @lornat75 @maggia80 @valegagge @ale-git @randaz81 @davege89
The text was updated successfully, but these errors were encountered: