summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge https://git-tails.immerda.ch/tails into doc/projectdoc/projectdoc/7536-projectTails developers2014-12-03794-21762/+46746
|\
| * Updating trace file after uploading 1.2.1.Tails developers2014-12-021-1/+1
| |
| * Addincremental upgrade path from 1.2 to 1.2.1 on the alpha channel.Tails developers2014-12-022-13/+28
| | | | | | | | | | This will make the manual testing of the incremental upgrade (for Tails 1.2.1) a lot easier.
| * Update calendar.Tails developers2014-12-021-12/+6
| |
| * Merge remote-tracking branch '451f/spriver/news_v1.2'Tails developers2014-12-021-42/+48
| |\
| | * minor improvements of sprivers translation of release notes 1.2Tails developers2014-12-011-42/+48
| | |
| * | Make it clear that check_po.sh's output and exit code are now part of its ↵Tails developers2014-12-021-0/+4
| | | | | | | | | | | | public API.
| * | Use single quotes unless double quotes are necessary in check_po.sh.Tails developers2014-12-021-1/+1
| | |
| * | Make check_po.sh `set -u' compatible, and then use it.Tails developers2014-12-021-7/+7
| | |
| * | Use quoting more consistently in check_po.sh.Tails developers2014-12-021-2/+2
| | |
| * | Prevent echo from adding a newline.Tails developers2014-12-021-2/+2
| | | | | | | | | | | | | | | Otherwise, even with empty i18nspector output, we triggered !0 exit code, and an empty line in the script's output.
| * | Add missing quotes.Tails developers2014-12-021-1/+1
| | |
| * | Make check_po.sh exit with 0 iff. the filtered i18nspector's output was empty.Tails developers2014-12-011-7/+10
| |/ | | | | | | | | | | | | | | | | It'll allow easier integration within our CI thingies. This change has the drawback that we're buffering output, and displaying it only once all i18nspector processes have completed. I say it's acceptable, now that their accumulated runtime is quite low. There might be a way to do this better, with some trick to capture stdout without buffering it.
| * Skip blank lines from the find|xargs i18nspector pipeline output.Tails developers2014-12-011-0/+1
| | | | | | | | For some reason, this new version outputs a dozen of blank lines or so.
| * Seriously optimize check_po.sh: avoid forking a python3 per PO file.Tails developers2014-12-011-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We currently have more than 800 PO files. The previous code ran i18nspector (and thus forked a python3 interpreter) for each of those. Let's now: * run as many i18nspector in parallel as the system has CPU cores * pass as much as 64 files to i18nspector at a time (on a system with 4 cores, we should ideally pass a bit more argumants at a time; on a system with 8 cores, we're close to the optimal theoretical setting; on a system with 16 cores, 64 at a time is a bit too much) On my system, total runtime has dropped from 73s to 3.8s.
| * Fix <<EOF syntax.Tails developers2014-12-011-4/+4
| |
| * Update Vagrant memory usage figures.Tails developers2014-12-011-3/+3
| |
| * Remove workaround instructions for #6514.Tails developers2014-12-011-2/+0
| | | | | | | | | | | | That bug was fixed almost a year ago, and the current instructions makes it look like you always should build with all proxy caching disabled.
| * Quote code more consistently.Tails developers2014-12-011-14/+14
| | | | | | | | Nowhere else are we using the $/# convention.
| * Suggest a safe workaround for installing Vagrant.Tails developers2014-12-011-18/+68
| | | | | | | | | | | | | | While we're at it, provide code that can be copy-pasted for the "add sources/pinning" instructions, to make the setup even easier. We also fix the sections so it's clearer what should be done for each supported Debian release.
| * Separate build instructions that apply for both wheezy and jessie.Tails developers2014-11-301-0/+4
| |
| * Also pin vagrant version 1.4.3+dfsg1-3 in Jessie.Tails developers2014-11-301-1/+1
| |
| * describe installing vagrant from debian snapshotsKill Your TV2014-11-301-5/+13
| | | | | | | | | | The versions of vagrant currently in Debian cannot be used to build Tails.
| * Add live system that provides a Dockerfile for easier building.Tails developers2014-11-301-0/+2
| |
| * Add info wrt. what people use to build cloud images (Closes: #7529).Tails developers2014-11-301-0/+14
| |
| * Fix ticket numbers.Tails developers2014-11-301-2/+2
| |
| * Update Vagrant situation in Tails and Debian.Tails developers2014-11-301-8/+3
| |
| * Add Docker availability (Closes: #7532).Tails developers2014-11-301-1/+24
| |
| * We only do the agenda hereTails developers2014-11-301-5/+2
| |
| * Update meeting agendaTails developers2014-11-301-5/+6
| |
| * Dont't mention date in titleTails developers2014-11-301-1/+1
| |
| * updated PO filesamnesia2014-11-303-6/+13
| |
| * Make title more explicitTails developers2014-11-301-1/+1
| |
| * updated PO filesamnesia2014-11-303-3/+34
| |
| * Warn users that OTR file transfers are not encryptedTails developers2014-11-301-1/+7
| |
| * Partially revert "Disabled comment plugin"Tails developers2014-11-291-0/+1
| |
| * updated PO filesamnesia2014-11-2914-94/+57
| |
| * updated PO filesamnesia2014-11-284-35/+290
| |
| * Translate a title and one sentence.Tails developers2014-11-282-4/+4
| |
| * Have the home and news pages include the correct file.Tails developers2014-11-286-12/+39
| |
| * Merge remote-tracking branch 'origin/web/8213-call-for-donations'Tails developers2014-11-2812-0/+859
| |\
| | * Updated PO filesTails developers2014-11-286-0/+714
| | |
| | * Move highlight CSS to local.cssTails developers2014-11-282-19/+19
| | |
| | * Move donation highlight to a place where it can be translatedTails developers2014-11-283-2/+2
| | |
| | * Add info about testimonialTails developers2014-11-281-1/+1
| | |
| | * Fix includesTails developers2014-11-272-2/+2
| | |
| | * Adjust datesajolida2014-11-271-1/+1
| | |
| | * Move include outside of /newsTails developers2014-11-271-0/+0
| | |
| | * Use ikiwiki linkTails developers2014-11-271-1/+1
| | |
| | * Fix typographysajolida2014-11-271-1/+1
| | |