| Commit message (Collapse) | Author | Age |
| ... | |
| |\ \ |
|
| | |\ \
| | |/
| |/| |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The command used to filter the file and its commit history from
bridgedb.git was:
$ git filter-branch -f --index-filter \
'git rm --cached -qr -- . && git reset -q $GIT_COMMIT -- doc/proposals/XXX-bridgedb-database-improvements.txt' \
--prune-empty \
--parent-filter 'ruby /home/isis/scripts/git-rewrite-parents.rb $@' \
--tag-name-filter cat -- --all
with the `git-rewrite-parents.rb` script, taken from
http://www.spinics.net/lists/git/msg177988.html, containing:
old_parents = gets.chomp.gsub('-p ', ' ')
if old_parents.empty? then
new_parents = []
else
new_parents = `git show-branch --independent #{old_parents}`.split
end
puts new_parents.map{|p| '-p ' + p}.join(' ')
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | | |
bridgedb/1606-bridgedb-spec
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The git filter-branch command used on the bridgedb.git repo was:
$ git filter-branch -f --index-filter \
'git rm --cached -qr -- . && git reset -q $GIT_COMMIT -- doc/bridge-db-spec.txt' \
--prune-empty \
--parent-filter 'ruby /home/isis/scripts/git-rewrite-parents.rb $@' \
--tag-name-filter cat -- --all
|
| | |/ |
|
| |
|
|
| |
svn:r12771
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
* FIXES #10614
|
| | | |
|
| |\ \ |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This specification should end at the point where clients have downloaded
all directory information they need. Using this information should be
covered in path-spec.
This results in the following changes to section numbers:
* 6 -> 5.4
* 6.1 -> 5.4.1
* 6.2 -> 5.4.2
* 6.3 -> 5.4.3
* 6.4 -> 5.4.4
* 6.5 -> 5.4.5
This commit does not yet repair subsequent section numbers.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
"Managing downloads" is not an operation of its own. Distribute the
consensus specific parts to 5.1 and the router descriptor specific parts
to 5.2.
This commit does not yet repair section numbering or references.
|
| | | |
| | |
| | |
| | | |
It's obvious that clients are storing router descriptors they downloaded.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
"General-use HTTP URLs" is not an operation but a reference, and
references belong in the appendix.
This commit does not yet repair section numbering or references.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Section 4.1 "Voting" describes much more than just the voting operation.
Move these operation fragments to the subsections they belong in.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Section 3.7 should only contain parts that are relevant for authorities,
and section 4.5 should only contain parts that are relevant for caches
(right now, it also describes what clients should do, but that's something
to change when cleaning up 4.5).
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This commit does not yet repair section numbering or references.
|
| | | |
| | |
| | |
| | | |
Take out cache-only parts from 3.6 and authority-only parts from 4.3.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This commit does not yet repair section numbering or references.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This subsection is just a placeholder for now.
Also fix section numbers and references.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The vote status document format (3.5) and the process of assigning flags
in a vote (3.6) are both part of the authority operation "exchanging
votes" and not operations on their own. That's why they should be
subsubsections rather than subsections.
This results in the following changes to section numbers:
* 3.5 -> 3.4.1
* 3.6 -> 3.4.2
* 3.7 -> 3.5
* 3.8 -> 3.6
* 3.9 -> 3.7
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This commit does not yet repair section numbering or references.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Phrase subsection title as operation. Also, remove subsubsection implying
that there would be other subsubsections in the future, which is not the
case.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This commit does not yet repair section numbering or references.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Section 3 will describe operations and data formats that are related
to the authority role, and section 4 will specify which operations are
performed by caches. Reflect this in the new section title of section
3, and remove the (already obsolete) overview part listing which
documents are generated by authorities.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The rule we're trying to follow here is that sections are for roles
(client, authority, cache, client) and subsections are for operations
performed by the role. Routers really only perform a single
operation: they periodically upload their descriptors to the
authorities. That's why there should be a single subsection for this
operation.
This effectively substitutes section number parts "2." with "2.1.":
* 2 -> 2.1
* 2.1 -> 2.1.1
* 2.2 -> 2.1.2
* 2.2.1 -> 2.1.2.1
* 2.3 -> 2.1.3
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Prefix all section references with the word "section", and avoid line
breaks between "section[s]" and section numbers.
Searching for section references should now be as easy as (for
example):
grep "section.* 1\.4" dir-spec.txt
Also, while going through section references, lower-case 1 instance of
"Section" to be consistent with the rest and fix 2 broken references.
|
| |/
|
|
| |
https://lists.torproject.org/pipermail/tor-dev/2014-January/006022.html
|