Am Samstag, den 03.12.2005, 13:43 +0100 schrieb Martin Fuchs:
What about all three informations: a.) author b.) affected directory, like "[dlls/ole32]" c.) beginning of the changelog
IMHO, best of all is starting with the affected directory and use the subject for c.
Benefit: Simple sort "by Subject" and the changes for a specific dll/program are all together, no matter, who created the Patch.
An example would be: "Michael Jung: [dlls/shell32] Implemented scrolling during drag&drop for the shellview class"
"dlls/shell32 [Michael Jung] Implemented scrolling during drag&drop for the shellview class"
Another idea would be to replace b.) and c.) by the original patch mail subject. This typically already contains the affected code section, for example "WINED3D: Return the correct parent in IWineD3DPixelShaderImpl_GetParent".
---- So, if the part before the colon has no space, try it as a path when not found, try to prefix with "dll/" or "programs/"
When the part is valid, use it as the start of the commit-Subject. When the part is invalid, use the Path of the First affected File as the start of the commit-Subject. ---- Your Example: "WINED3D [Creator] Return the correct parent in IWineD3DPixelShaderImpl_GetParent"