Thanks for your tip, this looks very useful =)
But how do I do this in practice? Do I need to write some kind of script
that monitors SVN and checks for new commits? Or is it possible to make SVN
to start such a script for each commit? Does someone have any best practices
here? What scripting languages are used (I am mostly familiar with Java)?
Thanks again,
Erling (newbie :)
On Thu, Feb 21, 2008 at 3:06 PM, prakash tiwary <prakash.tiwary_at_gmail.com>
wrote:
>
> Hi Erling,
> I think,You can use post commit hook from there you can can call "svn
> propset " to modify the log message in certain format.
>
> For example:
> svn propset -r * revision no* --revprop svn:log new message *URL*
>
> For further informations:
> http://subversion.tigris.org/faq.html#change-log-msg
>
> I wish it will help you.
>
> Thanks & Regards
> Prakash
>
>
>
> On Thu, Feb 21, 2008 at 4:07 PM, Erling Wegger Linde <erlingwl_at_gmail.com>
> wrote:
>
> > Hi,
> >
> > I'm trying to abstract away different bug trackers such as Jira and
> > Trac. If you use their respective Subversion Plugins - Jira relates
> > "PROJECT-2" and Trac #2 to their respective issues. I would like to provide
> > a uniform way for the user to add Issuekeys to the commit-log such as
> > project/2. Furthermore to allow the Trac and Jira subversion plugins to
> > recognise these tags I need subversion to expand the commitlogs.
> >
> > An example:
> >
> > The user enters "this issue is related to project/3"
> > Subversion expands this commit log to : "this issue is related to
> > project/3 PROJECT-3 #3".
> >
> > Is it possible to tell subversion to do this (hopefully without
> > recompiling - configuration or add-on /plug-in mechanism would be preferred)
> > and how?
> >
> > Any ideas / suggestions would be deeply appreciated!
> >
> > Thanks, Erling
> >
>
>
--
Med vennlig hilsen
Erling Wegger Linde
--
Med vennlig hilsen
Erling Wegger Linde
Received on 2008-03-02 18:06:57 CET