paul at jakma
Mar 21, 2011, 4:27 AM
Post #1 of 1
(153 views)
Permalink
|
In order to make life easier for maintainers, please consider
including an appropriate commit message. The current norms for these,
for Quagga, are documented in the HACKING file:
http://code.quagga.net/cgi-bin/gitweb.cgi?p=quagga.git;f=HACKING;hb=master
in the "COMMIT MESSAGES" section. The "PATCH SUBMISSION" section may
also be useful.
Please do try to provide a useful summary-line (first line of the
commit mesasge), as this makes it much easier to create the release
summaries using "git log --oneline". Please try to prefix the line
with a suitable tag to indicate which part of the code is affected
(e.g. "bgpd", "lib", "build"). Try to be regular, if suitable - a
quick look at "git log --oneline" will show you what useage is
typical.
We're not using "sign-off" lines in Quagga at the moment.
HACKING is a living document, please do feel free to suggest changes
to it here for discussion.
regards,
--
Paul Jakma paul [at] jakma twitter: @pjakma PGP: 64A2FF6A
Fortune:
Remember, God could only create the world in 6 days because he didn't
have an established user base.
_______________________________________________
Quagga-dev mailing list
Quagga-dev [at] lists
http://lists.quagga.net/mailman/listinfo/quagga-dev
|
