On 2011/09/22 18:37, Steven Blackburn <st...@beeka.org> wrote: > I take your point that the commit message could be more verbose, however > most commit messages I make in my day job tend to read more like a newspaper > headline (rather than have the story with the details of how and why the > change was done). The MPD git repo suggests similar usage.
You're missing my point, let me try to clarify. You obviously thought your patch needs a long explanation, which is why you wrote a lengthy email explaining it. My point is: if you think your patch needs a long explaination, then the right place to do it is the patch description, not an accompanying email. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
