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 380
    • Issues 380
    • 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
  • #2003
Closed
Open
Issue created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

TortoiseMerge uses wrong EOL with patches

By git... on November 20, 2013 05:41 (imported from Google Code)


What steps will reproduce the problem?

  1. Get a patch serial made on a linux box
  2. Review patch on windows
  3. When you apply parts of the patch, it uses mixed type EOL

What is the expected output? What do you see instead?
It should use the same EOL character the base file is in, not have both LF & CRLF line endings

What version of TortoiseGit and msysgit are you using? On
what operating system?
TortoiseGit 1.8.6.0
git version 1.8.4.msysgit.0

Please provide any additional information below.

Patch file is LF, base file is CRLF (windows)
When review patch, as can be seen by the picture, patch file is ALL LF.
Original file is ALL CRLF (windows)
If we use the patch's data, then it gets the file to have both LF and CRLF, and that is bad.


PatchCapture.PNG

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