Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #17197

Closed (moved)
Open
Opened Oct 01, 2015 by teor@teor

Use CRLF for all text files written on Windows, accept either CRLF or LF on all platforms

In #17501 (moved), stem becomes confused because some text files written on Windows use CRLF, and others use LF.

We could use CRLF for all text files written on Windows, and accept either CRLF or LF on all platforms.

Here is a list of files from DataDirectory with their line endings on Windows:

CRLF cached-certs
CRLF cached-consensus
LF   cached-descriptors
LF   cached-descriptors.new
CRLF cached-microdesc-consensus
LF   cached-microdescs
LF   cached-microdescs.new
CRLF state

We might want to review all files written by tor, including those only written by hidden services and any other components.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#17197