On Tue, Jul 07, 2009 at 09:16:11AM -0400, Marty Jack wrote: > At some point we should get serious about having valid ChangeLogs. It makes > > distro packagers nervous when they can't readily evaluate what has changed > in> a release.
I also mused about ChangeLogs: We should not duplicate information already available in SVN to GNU ChangeLogs. Commit information is not really useful in plain text files. Adding references to files and functions as proposed in "GNU Change Logs Standards" is just crutch for manually maintaining commit information which is already handled much better by GIT or SVN. Even GTK+ as official GNU Project moved from GNU ChangeLog to auto-generated GIT ChangeLog for dist tarballs. I would propose to standardize commit messages to GTK+/GIT standard instead. Quote from GTK+ README.commits: ... * The expected format for git commit messages is as follows: === begin example commit === Short explanation of the commit Longer explanation explaining exactly what's changed, whether any external or private interfaces changed, what bugs were fixed (with bug tracker reference if applicable) and so forth. Be concise but not too brief. === end example commit === ... Jürgen ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/blackberry _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
