On 18/02/13 01:14, ChunEon Park wrote: > Could it possible to make git mail title messages to be more meaningful? > > i.e) [core/efl] xxxmaster updated. f27ff2fbf31a01c2f8d98e773bed6cc4298749bd > -> [core/efl/evas] xxxmaster updated. > f27ff2fbf31a01c2f8d98e773bed6cc4298749bd
I think after some discussion we all agree that the commit mails and titles need to change. I believe we have a sort of consensus now that we need to: * send one mail per commit * change the subject of the mail to include author and first line of commit message so: [EGIT] [core/efl] eina: fix siginfo detection (Cedric BAIL) * If we send mails for more than just master we should include the branch in the commit message Are we in favour of sending mails for all branches or just for master? Anything else I missed? > If the title shows any detailed core lib name that was changed, it would be > better to know what is changed in abstractly. I don't think that we can easily do that. We know the repository, but figuring out the component that changed is harder. What I am in favour of is prefixing the first line of the commit message with the part you're actually working on. (See example above) Regards, Daniel ------------------------------------------------------------------------------ The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
