Hi Henrik, At 13.33 07/08/2006, Henrik Nordstrom wrote:
mån 2006-08-07 klockan 13:04 +0200 skrev Guido Serassio: > Yes, I also prefer a solution without any special markup, but this > solution warrants that the commiter must know what is doing, and it's > a not so big effort like the old 2.5 patch management .... :-) What about the following simple rule First paragraph must be >20 characers and <120. If it doesnt start with Bug then it must additionally be >40 characers long and it must be followed by a second paragraph further explaining the impact of the change. i.e. a title and a description is required, separated.
This was my first idea, but the minimum title length could be a problem, just some changelog examples:
Memory leak on pinned connections Documentation update Cosmetic linewrap layout fixes Forgot some small changes Preparing 2.6.STABLE2 Ran indent What about an optional tag allowing a minimum length override ? Regards Guido - ======================================================== Guido Serassio Acme Consulting S.r.l. - Microsoft Certified Partner Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/
