Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Wiki Replica
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
TPA
Wiki Replica
Repository graph
Repository graph
You can move around the graph by using the arrow keys.
e5e84236b5072cb28f630b1ab62bcc32f8163903
Select Git revision
Branches
7
master
default
protected
mkdocs
new-blog-doc
puppet-merge-costs
rfc-77-improv
tails-merge-admin-mailing-lists
tpa-rfc-80-merge-tor-and-tails-support-policies
7 results
Begin with the selected commit
Created with Raphaël 2.2.0
15
Jun
11
10
4
3
2
28
May
27
26
25
22
20
18
13
12
11
10
8
6
4
1
30
Apr
29
28
27
22
21
20
18
16
15
14
13
9
8
3
2
1
31
Mar
30
27
25
23
21
19
17
16
13
12
10
9
4
2
28
Feb
25
24
21
20
19
13
12
11
10
8
7
4
3
31
Jan
30
29
28
27
23
22
21
20
17
16
15
14
13
10
9
7
19
Dec
18
16
13
12
2
28
Nov
26
25
22
20
19
18
16
15
14
13
11
7
6
5
4
3
1
31
Oct
30
29
28
26
25
24
23
22
21
18
17
16
15
13
12
11
10
9
link syntax
gitlab migration intro
Add documentation for gitlab backups
add gitlab documentation from template, with some mig notes
clarify there is no established timeline for the gitlab wiki migration
gitlab policy proposal
spell check
mark a deadline
make reference links so this looks better in email
sysadmin meeting minutes
a reboot is needed as well
clarify that the issue tracker will change
add section specifically about adding disks
make more explicit headers in instance modification
add missing bracket
add warning about ping in cloud installer
move to "two people" for service support qualification
another link fix
fix cross-refs
more cross-references
expand summary
rephrase background a little
merge the two supported service criteria definitions
clarify operating system requirement for service transition
refer to the service documentation template
make a numbered list of requirements for services
word wrap
add direct link for service admins
move how-to-get-help up to a section heading
clarify the relation between the policy and the questionnaire
also move how-to-get-help policy along with TPA-RFC-2
merge the service admin definition in TPA-RFC-2
move supported services out of the service level section
expand the background section
fix table of contents to follow policy
Add documentation on how to update a user's key.
make actually needs root
use alberti's alias (db)
opened a ticket about formalizing our archive
deb: make the ssh make command a post-upload hook
Loading