Bugtraq.logregex breaks escaping slash
By hFFFFF... on June 09, 2011 20:27 (imported from Google Code)
What steps will reproduce the problem?
- Create git repo
- Open TortoiseGit settings window via context menu on repo's root folder
- In the "Hook Scripts" group select "Issue Tracker Config" item
- Fill "bugtraq.url" with something like "https://my.issue.tracker/issue?%BUGID%"
- Type into "bugtraq.logregex" field regular expression with escaping slash, i.e. "(MyProject|AnotherProject)-\d+)"
- Set radio buttons: warningifnoissue=true, append=false, number=false
- Continue using TortoiseGit, sometimes skip issue number and ignore warning messages on commit
What is the expected output?
Function simply works until settings will be manually changed.
What do you see instead?
First time it works well, but after a few days someone (I suspect TortoiseGit) turns over the slash symbol in "logregex" replacing escaping "" to dummy "/", so TortoiseGit starts to warn even commit message contains an issue number. When I open the settings dialog I see broken regex: "(MyProject|AnotherProject)-/d+)". I fix that expression turning back the slash, but after some time it breaks down again.
What version of the product are you using? On what operating system?
TortoiseGit: 1.6.5.0 (both x86 and x64 versions installed)
msysgit: 1.7.3.1
OS: windows 7 x64
Please provide any additional information below.
Sorry, I couldn't find, what exactly causes this. I just use local git repo with remote svn server (via git-svn). I just do usual operations (work and commit to local branch, merge to master, dcommit to svn, fetch and rebase from svn) and all things go right, then during another commit TortoiseGit warns about missing issue number in correct commit message with issue number. After fixing problem repeats few days later.