[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Issue Tracker Integration

From: Alexander Klenin <klenin_at_gmail.com>
Date: Sat, 19 Jan 2008 23:09:56 +1000

On Jan 3, 2008 1:18 AM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:

> >> Previous requests like this suggested that the issuetracker itself
> >> would provide all the open/assigned issues as an xml file which TSVN
> >> should then parse and show to the user. But of course, using COM isn't
> >> a bad idea.
>
> > Could you point me at (or explain) this concept? I had a search through
> > the mailing list before I posted this, but I didn't find anything that
> > seemed appropriate.
>
> The idea was that we could define some xml schema which the various
> issue trackers then would have to implement/provide. But I guess apart
> form the open source trackers, others wouldn't implement this anyway.

Sorry for the late reply. I was on a vacation, and I am just catching
up with the January e-mail.
Issuetracker-to-TortoiseSVN integration is indeed a welcome feature.
However, I wonder about the necessity of using COM for that.
How about extending "Start commit" hook interface instead?
I propose:
1) Allow %MESSAGEFILE% parameter in Start commit hook.
The hook should write an initial message text to that file.

2) Add %BUGID% (%BUGIDFILE%?) parameter --
a file where the hook should write bug ID(s) for this commit.

This idea seems much simpler to me, while allowing essentially the
same functionality.

-- 
Alexander S. Klenin
Insight Experts Ltd.
Received on 2008-01-19 14:10:02 CET

This is an archived mail posted to the TortoiseSVN Dev mailing list.