[Libre-soc-bugs] [Bug 1126] How to document new bugs/issues

[bugzilla-daemon at libre-soc.org]

https://bugs.libre-soc.org/show_bug.cgi?id=1126

--- Comment #50 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(In reply to Dmitry Selyutin from comment #40)
> I suggest we stick to some simple rules upon formatting git commits:
> 
> 1. Every commit MUST start with a short title, up to 50 characters.
> 2. The coomit title MUST contain either subsystem, or a file path, or a
> subsystem/path, or a subsystem/subsubsystem combination, which got modified
> or introduced, 

risk: "added file X. changed file Y". the commit diff shows you
precisely and exactly that. it is considered bad practice.

better: bugNum: summary.

if people are not referring to the actual bug for context we have a
serious problem.

in any series of commits i tend to make sure one of them has the
full bugrport URL. it generally depends on how important the change
is as to whether i put the full URL or not

-- 
You are receiving this mail because:
You are on the CC list for the bug.