Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • Trial Trial
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LI - Lawful Interception
  • TrialTrial
  • Issues
  • #7

Closed
Open
Created Aug 17, 2020 by baxterp@baxterpDeveloper

Last pre-5G version of 102232-1 from LI#49 Zagreb meeting has wrong line endings (as does all of 102232-2)

c2ff3aee

Mostly 102232-1 asn1 versions are OK, except this one. New (renamed) file is stored with old style mac line endings.

This is the last version snapshot before 5G kicks in so worth getting right?

Also appears that most (all?) of 102232-2 checkins also suffer from this line ending problem. Also checked other TCLI folders and these appear OK at least at head (didn't go back into histories)

Viewing in gitlab on screen looks OK until you try and copy the file then you get extra empty lines. Gitlab WebIDE view also shows the problem, as does copying of files via various mechanisms.

Gitlab has a known issue that it tracks the input EOL rather than normalising. So mac based check-ins can be problematic.

Workaround - as rewriting git history is fiddly Checkout as is with the mixture of \r (mac) followed by \n\r (win) Use your favourite editor to replace \r\n with \n - file will now be correct as a win file Maybe trim trailing spaces? Save as corrected file

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