I think that is a terrific idea. It might be prudent though to limit the commit messages posted here to changes that impact files in the core/ directory only, to avoid what for most people might be off-topic clutter. (since that subversion repository is well... a complex beast to put it nicely).
Saq On Apr 6, 6:26 pm, "[email protected]" <[email protected]> wrote: > I hear tell this has been discussed in the past, but I thought I would > bring it up again as it's something I rather miss. > > I am a _huge_ fan of verbose commit messages. I think they provide all > kinds of functionality for both the author and audience of the > changeset. For both they help to explain what is going on. For the > author they force them to articulate what they did in clear language, > which can expose flaws and help set the stage for whatever is needed > next. For others they provide a fulcrum for future discussion and > discovery. > > In the TiddlyWiki universe commit messages basically get sent into the > void of Trac. They do nobody any good there, where they can't be > conversation generators. > > The standard process in other communities is that a post commit hook > is used in the repo to send the commit message and a diff to a mailing > list whereupon people in the community can see it and say things like: > > * you're doing it completely wrong[1] > * wow, I did not know that, I've learned something > * wouldn't it be better if you did it like X? > * etc > > Can we do this? > > [1]http://www.xach.com/img/doing-it-wrong.jpg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/TiddlyWikiDev?hl=en -~----------~----~----~----~------~----~------~--~---
