Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,018
    • Issues 1,018
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • Tor Browser
  • Issues
  • #40024
Closed
Open
Created Jul 07, 2020 by Georg Koppen@gkDeveloper1 of 1 task completed1/1 task

Go over rebased patches again and reorder pieces where needed after rebase to esr78 is done

We've reordered/squashed bits of our patch set during #31918 (closed). We should do this again once we have the rebasing to esr78 done and are happy with the results.

@acat noted in #33533 (closed): One example that comes to my mind for this is the security level patch, which introduces a localization mecanism which is later replaced by TorStrings.jsm in the #31286 (closed) patch.

Additionally, there are firefox-branding.js changes that moved to the updater related patch. We might want to think about something that's less surprising. 🙂


  • #40047 (closed)
Edited Aug 07, 2020 by Georg Koppen
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking