Bernd Steinhauser schrieb:
Ingmar Vanhassel schrieb:
So a commit message should have one line as a summary and if needed,
more
information in the following lines.
BTW, I would vote for including a diffstat.
Might be useful as well.
You mean instead of what we currently do, just listing the files
modified,changed,removed?
Yes, because it contains more information using (nearly) the same space.
And it is better readable, imo.
For example:
packages/sys-libs/pam/ChangeLog | 7 +++++++
packages/sys-libs/pam/files/pam.d/other | 4 ++++
packages/sys-libs/pam/files/pam.d/system-auth | 12 ++++++++++++
.../sys-libs/pam/files/pam.d/system-local-login | 4 ++++
packages/sys-libs/pam/files/pam.d/system-login | 18
++++++++++++++++++
.../sys-libs/pam/files/pam.d/system-remote-login | 4 ++++
...{pam-1.0.1.exheres-0 => pam-1.0.1-r1.exheres-0} | 14 ++++++++------
7 files changed, 57 insertions(+), 6 deletions(-)
instead of:
* +files/pam.d/other, +files/pam.d/system-auth,
+files/pam.d/system-local-login, +files/pam.d/system-login,
+files/pam.d/system-remote-login, +pam-1.0.1-r1.exheres-0,
-pam-1.0.1.exheres-0
Just a note, why I do think, that this additional information is helpful:
Lets say, that an ARCH member marks the package stable and says so in
the Changelog entry.
As a maintainer, if you see, that there is more than one line changed,
you might get suspicious and have a deeper look.
Bernd
_______________________________________________
Exherbo-dev mailing list
[email protected]
http://lists.exherbo.org/mailman/listinfo/exherbo-dev
