On Fri, Apr 28, 2006 at 05:30:24AM -0700, Dermot McCluskey wrote: > - Subject contains "<SCM identifer> <Repository>/<Module> <Author>" > eg: "SVN commit: jds/spec-files dermot". Possibly add > Revision/Transaction Id, but nothing else.
Much more useful is a (shortened if necessary) summary of the changeset. I've been mangling Teamware commits like this for ages, and it's so much easier to pick out what might interest you. In mutt it looks like this: 5116 01/10 John Levon (0.9K) 6330561 ::cpuregs/stack should take cpu_t's, 6330593 ::cpustack can fault kmdb (Note that the email should appear to come from the committer, so you don't need "author" in the subject either). Presumably "/<Module>" will not be present for mercurial changesets. I don't see the point in the "SVN" bit. Why is that important enough to put in the Subject? > - Commit mails should *not* contain diffs of modified files - > too much detail. As others have mentioned, that's fine, but there should be some URL with the specific changes in. > 2006-04-28 Tom Smith <[EMAIL PROTECTED]> > > * gnome-menus.spec: Update. > * patches/gnome-menus-03-application-submenu-rename.diff: New > patch to rename a few submenus to Universal Access and > Developer Tools. Clearly, the "subject contains summary" thing doesn't work too well for such formats. It does, however, work well for typical ON commits... regards john _______________________________________________ tools-discuss mailing list [email protected]
