Hello. On 18/02/13 09:21, Tom Hacohen wrote: > On 18/02/13 04:02, Daniel Juyung Seo wrote: >> And it'll be great if the title includes the first line of commit > message. >> That should be way more useful. >> Thanks. > > Correct me if I'm wrong, but I'm starting to think you guys would like > to see the whole diff in the title.
Come on. Take a step back and look at the commit email subject line as we have it right now: [EGIT] [core/efl] branch master updated. 04e660c5c76fa9168be08de1f979a1684c464154 [EGIT] Might be needed for people that can or want not filter on message headers. [core/efl] Gives the repo. Useful. branch master updated: I argued before that commit mails should only be send for the master branch. Everything else is only interesting for a small group of people and they will pull and look at the specific branches on their own. git hash: Not useful in the title I would argue. Gives you zero informations about what was changed. Needed in the body for sure, but not in the subject. I would propose: [EGIT] [core/efl] First line of commit message. The body does then have the full commit message, the hash as well as a shortlog before the complete diff comes in. And yes that means one commit should result in one mail. regards Stefan Schmidt ------------------------------------------------------------------------------ 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
