tails merge requestshttps://gitlab.tails.boum.org/sdibella/tails/-/merge_requests2021-04-12T19:19:43Zhttps://gitlab.tails.boum.org/sdibella/tails/-/merge_requests/4Sync our work2021-04-12T19:19:43ZcbrownsteinSync our workhttps://gitlab.tails.boum.org/sdibella/tails/-/merge_requests/3Sync our work2021-03-23T16:10:48ZcbrownsteinSync our workhttps://gitlab.tails.boum.org/sdibella/tails/-/merge_requests/2Redact summary for compromised computers article2021-03-04T13:43:40ZcbrownsteinRedact summary for compromised computers articleMy understanding from our last meeting with @sajolida is that each of the summaries should have 2 bullet points. Maybe 3 is fine, one for each heading in the main article.
I don't particularly like how I formatted the _Running Tails on ...My understanding from our last meeting with @sajolida is that each of the summaries should have 2 bullet points. Maybe 3 is fine, one for each heading in the main article.
I don't particularly like how I formatted the _Running Tails on a computer with a compromised BIOS or firmware…_ line. I feel it should be shorter.
You should be able to edit my changes using the Web IDE built into GitLab. That is probably easiest for making quick fixes.
For larger fixes, it might be better to accept this merge request and work on your local branch.https://gitlab.tails.boum.org/sdibella/tails/-/merge_requests/1Sync our work2021-03-03T17:37:42ZcbrownsteinSync our workHi @sdibella,
I've merged your work into my branch.
By accepting this MR (merge request), our work will be in sync, i.e., you'll have my latest work in your branch, just like I have your latest work in my branch.Hi @sdibella,
I've merged your work into my branch.
By accepting this MR (merge request), our work will be in sync, i.e., you'll have my latest work in your branch, just like I have your latest work in my branch.