On Fri, Dec 03, 2010 at 11:14:12AM -0500, Kohei Yoshida <kyosh...@novell.com> wrote: > My rationale: Many times when I work on feature branches, I commit stuff > but intentionally not provide documentation because the role of the > class/method/whatever may change during the course of the > implementation. This requirement would break my workflow, and I > wouldn't appreciate that. > > Encouraging good documentation is a must, but making it a requirement > even for new files unconditionally is bad.
Hm, what about enforcing it only in master / libreoffice-* branches? (Just an idea.)
pgpfhUAnKQeGx.pgp
Description: PGP signature
_______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
