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
  • #16033

Closed (moved)
Open
Opened May 15, 2015 by cypherpunks@cypherpunks

Silence some make rules

The make rules for generating the file micro-revision.i and changing the permissions of the test scripts are IMO not configured correctly.

The micro-revision generation rule runs on every call to make. Its function requires it to stay up-to-date to the current state of the repository. My question is whether the act of updating/generating the file needs to be communicated back to the user every time? IMO it clutters the terminal (especially on make check where the focus should be on the test results not on output of irrelevant make rules).

Changing the permissions of the test scripts should be silent IMO unless silent rules are disabled. It clutters up the terminal when running make check.

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