Re: [Geotools-devel] descriptive commit messages

2012-09-18 Thread Justin Deoliveira
On Mon, Sep 17, 2012 at 9:07 PM, Ben Caradoc-Davies < [email protected]> wrote: > +1. > > Thanks for bringing this up, Justin. Does the developer manual address > this matter? > I am not sure, i don't believe so. Perhaps something under here: http://docs.geotools.org/latest/developer

Re: [Geotools-devel] descriptive commit messages

2012-09-18 Thread Ben Caradoc-Davies
On 18/09/12 15:02, Andrea Aime wrote: > Agreed here too. I normally go to jira, open the issue, do "view xml" > and copy the > title field, which contains both jira number and title of the jira Thanks. A nice trick that avoids having to cut and paste multiple selection. -- Ben Caradoc-Davies So

Re: [Geotools-devel] descriptive commit messages

2012-09-18 Thread Andrea Aime
On Tue, Sep 18, 2012 at 5:07 AM, Ben Caradoc-Davies < [email protected]> wrote: > +1. > Agreed here too. I normally go to jira, open the issue, do "view xml" and copy the title field, which contains both jira number and title of the jira Cheers Andrea -- == Our support, Your Success!

Re: [Geotools-devel] descriptive commit messages

2012-09-17 Thread Ben Caradoc-Davies
+1. Thanks for bringing this up, Justin. Does the developer manual address this matter? I find commit messages with only the Jira key to be a lot less helpful than they could be. Developers, please think of another developer looking at a long log listing. Or a maintainer considering your pull

[Geotools-devel] descriptive commit messages

2012-09-17 Thread Justin Deoliveira
Hi folks, I have been noticing a few commit messages go by with no comment except for the jira number they are related. While this is efficient (less typing) it is also cumbersome for someone reviewing, or analyzing history to have to go back to jira to figure out what the context. At least a sent