On Monday 23 July 2007, Jason Winnebeck wrote:
> 
> -----Original Message-----
> From: Eli Carter
> 
> On Monday 23 July 2007, Jason Winnebeck wrote:
> > 
> > If we look at trac-hacks.org site, you can see in the timeline which
> > project (plugin) was modified in a changeset, with a header at the
> > beginning. Is this done at the SVN hook level or is it a plugin for
> > Trac; or, how can I achieve the same effect in my Trac? I have a
> similar
> > setup where I have top-level directories in the repository relating to
> > different projects/modules. It would be cool if I made a commit:
> > 
> > M /ProjectABC/trunk/src/file.txt
> > "Fixed a typo"
> > 
> > That in Trac it would display as "ProjectABC: Fixed a typo" similar to
> > how it occurs in trac-hacks. I figure since all the messages in
> > trac-hacks follow this form that there must be an automated method.
> > 
> > Any suggestions on the best approach?
> 
> I don't know how trac-hacks is setup, but I have something similar setup
> here.  
> In my case, it's a subversion pre-commit hook that modifies the log in
> the 
> transaction.
> 
> Eli
> 
> ---------------
> 
> Would you be willing to share the hook script? Basically what I was
> thinking if I went the script route is to use a regular expression to
> pull out the first path component and prepend it to the commit message
> if all paths modified matched in the same first component. But I'm not a
> script master and I'm new to the way that hooks work so if there's
> already something existing I can start from that or just use it if it's
> close to what I want.

I started from 
http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/log-police.py

Eli

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" 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/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to