- 11 Dec, 2013 10 commits
-
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
- 10 Dec, 2013 7 commits
-
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
- 09 Dec, 2013 22 commits
-
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
Taken at commit 51bf06502c46ee6c1f587459e8370aef11a3422d from the tor-browser-24.2.0esr-1 branch from https://git.torproject.org/tor-browser.git.
-
Tails developers authored
-
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
-
Tails developers authored
On the long run, we want to do this at build time, just like the TorBrowser. However, fiddling with the build options two days before a Tails release seems crazy, so let's disable this with a pref for now. Successfully tested on http://mozilla.github.io/webrtc-landing/ and http://net.ipcalf.com/.
-
Tails developers authored
-
Tails developers authored
Document that -l10n must be told about the release schedule as well, and write email addresses in full.
-
Tails developers authored
-
Tails developers authored
-
- 08 Dec, 2013 1 commit
-
-
Tails developers authored
-