Harald Hoyer wrote:
>>> Furthermore, when you click on "Choose Issue"-button and debug the
>>> "GetCommitMessage"-method, you will see, that the bugid-snippet is
>>> missing. Needless to say, it is also impossible for GetMessage to return
>>> something, that provides another bugid that will be recognized.
>> Yes, because it's not part of the message the user entered but
>> pre/appended to the message when the commit dialog is closed.
>>
>> You could use the IBugtraqProvider2 interface (available in 1.6) which
>> allows you to check the 'complete' message in the method CheckCommit().
>
> The solution you suggested, sounds a bit tricky to me. It would be nice, if
> could reconsider it. I don't want to check things. I have to modify the
> bugid. Why the full message with bugid-snippet could not be provided. Or you
> provide a way to get / set the bugid inside of
> IBugTraqProvider.GetCommitMessage. This would make the parsing rule
> transparent to IBugTraqProvider.GetCommitMessage.
You should consider using the bugtraq:regex property to define your
bugid. That way if you add a matching line to the commit message the
bugid field gets automatically filled in with that id.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1289716
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-03-08 16:05:42 CET