Ok just after sending the email I understood than second line (and only second line) should be empty.
It would actually be nice if those rules were somewhat more explicit, for example in the documentation (# message) during a git commit... On Fri, Jul 30, 2010 at 10:22 AM, Mathieu Malaterre <[email protected]> wrote: > Hi, > > I see that some people manage to get a commit line of more than just > a single line (78 chars), for instance: > > http://cmake.org/gitweb?p=cmake.git;a=commit;h=fbe67a9fda7c3a96a1774838cb13353b79443e56 > > if I try to do that on my side (git 1.6.5) I get either: > > ---------------------------------------------------------------------- > commit 6a3d7d46 has an invalid message: > the first line must not be more than 78 characters > commit message is: > BUG: 0009611 Fix Arch independent FindJNI.cmake on Linux to support > Sun Java, OpenJDK, Kaffe and GCJ paths. Based on patch from debian > ---------------------------------------------------------------------- > > or > > ---------------------------------------------------------------------- > commit b6ec0777 has an invalid message: > the second line must be empty (if it exists) > commit message is: > BUG: 0009611 Fix Arch independent FindJNI.cmake on Linux > support Sun Java, OpenJDK, Kaffe and GCJ paths. Based on patch from debian > ---------------------------------------------------------------------- > > Could someone please let me know what I am doing wrong ? > > Thanks > -- > Mathieu > -- Mathieu _______________________________________________ cmake-developers mailing list [email protected] http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
