On Tue, Aug 27, 2013 at 8:50 AM, Bob Archer <Bob.Archer_at_amsi.com> wrote:
>> > Isn't the Bug ID just a specially formatted part of the commit
>> > message? I.e. couldn't you just append whatever you need to the string
>> > passed to /logmsg or the file to /logmsgfile?
>> Hi Ben
>> Thanks for a quick response.
>> I dont know how to format the message so that it is treated as a bugid field.
>> When i issue the command
>> TortoiseProc.exe /command:copy ...
>> from the script, I'd like users to have the Bugtraq bugid field filled and have the
>> issue link URL filled as well.
>> I did not manage to find any info about the way the message in /logmsg: should
>> be formatted, to be interpreted by TSVN as a bugtraq bugid.
>> Also, since there is a switch /bugid:, why not make it available for all
>> commands that can modify data in SVN repository.
> Basically the bugid is used as a variable in the bugtraq:message property. You could just look at that property and duplicate how it uses the BUGID. As was said above, this is just appended to your commit message.
For example, suppose your bugtraq:message property is "ISSUE_NO: %BUGID%"
Then, when you commit, you can either fill in the ISSUE_NO dialog box,
or you can ignore that box and type "ISSUE_NO: 12345" at the end of
your commit message, and it will do (mostly) the same thing. I say
"mostly" because on my system it is configured to prompt if the bug ID
is missing, and it still prompts me when I type it out in the comments
even though after the commit there is no difference at all between
that and using the dialog entry field.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-27 16:51:28 CEST