+1 for me.
I'd also like to encourage everybody to be sensible when squashing
commits (e.g. when merging a pull request). Apart from loosing
information in the commit messages it makes it harder to revert parts of
a pulled branch.
Regards,
Matthias
On 12/11/2012 01:26 AM, Werner Macho wrote:
+1 from me !!!
(although I don't see the necessarity of writing more than one line
when updating some language files ;) )
regards
Werner
On Mon, Dec 10, 2012 at 9:14 PM, Sandro Santilli <[email protected]
<mailto:[email protected]>> wrote:
Dear qgis committers, may I ask you to make your commit logs
more verbose than a bare ticket number reference ?
It is nice to be able to know what's going on by simply reading
the git log, without the need for a network connection and
a running and live bug tracker.
Also commands like `git log --grep=<some_keyword>` become nearly
useless if the commit log contains no description of what's changed.
Ideally the log would have 1 line with short description and a
longer description in a second paragraph. Note that this format
is also expected by `git format-patch` which turns the first line
into a mail subject and the subsequent paragraph to the body.
Also github pull requests use the same semantic for interpreting
the log.
Thanks everyone for your attention to source repository quality :)
--strk;
_______________________________________________
Qgis-developer mailing list
[email protected] <mailto:[email protected]>
http://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
