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

Closed (moved)
Open
Opened Sep 28, 2017 by Georg Koppen@gk

Adapt the README.HACKING document to allow the user to modify the correct git_hash when testing branches/commits

I tried to test the patches for #16778 (moved) and did the following in my tor-browser-build repo

-git_hash: 'tor-browser-[% c("var/firefox_version") %]-[% c("var/torbrowser_branch") %]-1-build2'
-tag_gpg_id: 1
-git_url: https://git.torproject.org/tor-browser.git
+git_hash: 'bug16778_v2'
+tag_gpg_id: 0
+git_url: https://github.com/sysrqb/tor-browser

After doing a |make fetch| and |make testbuild| the new commits are not used. I verified that by inspecting the .tar ball we use in our container for building.

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