> Deciding on a _commit policy_ should be fairly straightforward and we > already have one point > * gpg sign every commit (unless it's a merged branch, then we only care > about the merge commit)
+1 > More things to consider for commit policy are: > * commit message format (line length, maybe prepend category/PN?) this could be done in part by repoman... having a meaningful shortlog would be nice. > * do we expect repoman to run successfully for every commit (I'd say no)? commit no, push yes? > * additional information that must be provided > * when to force/avoid merge commits my take- disallow (by policy) nontrivial rebases by third parties, encourage trivial rebases -- Andreas K. Huettel Gentoo Linux developer (council, kde) dilfri...@gentoo.org http://www.akhuettel.de/
signature.asc
Description: This is a digitally signed message part.
