Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • TortoiseGit TortoiseGit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 382
    • Issues 382
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGitTortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #2113
Closed
Open
Issue created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

JiraSvn bugtraq provider's commit behavior is broken after #1979

By andrew.nefed... on February 17, 2014 15:53 (imported from Google Code)


What steps will reproduce the problem?

  1. Have JiraSvn bugtraq provider configured for a repo.
  2. In the commit dialog open the provider's dialog and select some issue(s).
  3. Ensure some lines (with issues references and a trailing newline) are added to the commit message.
  4. Do the commit.

What is the expected output? What do you see instead?
Corresponding Jira issues have a comment with the original user-entered message. Instead, full commit message (including this added lines) is posted to the Jira issue.

What version of TortoiseGit and msysgit are you using? On
what operating system?
TortoiseGit 1.8.6.3+

Please provide any additional information below.
The problem started to occur after fixing issue #1979 (closed).
When the provider adds its lines to the message it remembers (literally) what it has added and when committing it compares the message against this added "tail" trying to find end position of the original message.
But now the commit message started to loose trailing newlines so the providers is unable to find its own lines and assumes a user has modified the message thereafter.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking