It appears to me that with only one svn for all of the projects, the commit messages are not so helpful since you don't know (from the commit message itself) which project's files are affected by the commit.
==>> Because of the above, should we try to establish a convention of prepending the project name to ALL commit messages? Eg instead of "added some comments" "Timeline: added some comments" Wiki changes (Thanks rdq123!) would be prepended "Wiki: xxx" The automatic checkin messages (sent to the dev list), do include the directory path of one of the files changed during the checkin. But while that helps somewhat, prepending the project name would help by enabling a quick scan of the commit messages to find which commits are about which projects. Thoughts? Regards, Larry K --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SIMILE Widgets" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/simile-widgets?hl=en -~----------~----~----~----~------~----~------~--~---
