Please apply :)
Cheers,
BitingBird
>From 92bafd59781f5daec24084b218536c6defc50447 Mon Sep 17 00:00:00 2001
From: Tails developers
Date: Mon, 23 Feb 2015 04:19:16 +0100
Subject: [PATCH 2/2] anchor for accessing internal hard disk
---
.../your_data_wont_be_saved_unless_explicitly_asked.mdwn
BitingBird wrote (22 Feb 2015 23:11:58 GMT) :
> Please apply the patch, so I can correct the link in the 2014 report :)
Merged, thanks!
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this lis
Please apply the patch, so I can correct the link in the 2014 report :)
BitingBird
>From f3a1f65fc43c53086e79ba198c24572a83a062d5 Mon Sep 17 00:00:00 2001
From: Tails developers
Date: Mon, 23 Feb 2015 00:07:36 +0100
Subject: [PATCH] correct anchors in secure deletion
---
wiki/src/doc/encryptio
Hi, intrigeri. Sorry it's taken a while to respond, you gave me a lot
to think about. The potential lack of VT-x/d implies that any
virtualization solution should be based around tor browser or whatever
you're currently using, which I am fine with. I think it will be
feasible to run the tor brow
sajolida wrote (22 Feb 2015 20:12:23 GMT) :
> What if we need to publish an important workaround for a bug in 1.3?
On the website? As an emergency point-release? Anything else?
Anyway, good question, and probably it doesn't change much my answer
below:
> Would "you" (the people locking the repo)
intrigeri:
> Questions?
What if we need to publish an important workaround for a bug in 1.3?
Would "you" (the people locking the repo) be still able to do some
emergency commits to it?
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.o
On 02/22/2015 05:47 PM, intrigeri wrote:
> Looks good. Pushed a few minor rephrasing and formatting improvements.
Cheers!
> There's one confusing point, though: somewhere it is said that merged
> branches can be deleted "After a new Tails release has been shipped",
> while elsewhere I see "it can
sajolida wrote (22 Feb 2015 17:14:20 GMT) :
> intrigeri:
>> Please have a look and shout if there's something in there that we
>> should keep.
> All of mine can be deleted. Sorry for the mess.
Just to confirm, since what you're quoting is another, different
question -- were you replying to that q
Hi,
Please review'n'merge into testing and devel.
Cheers!
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
tails-dev-unsubscr...@boum.org.
intrigeri:
> Please have a look and shout if there's something in there that we
> should keep.
All of mine can be deleted. Sorry for the mess.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from
Jurre van Bergen:
> Hi folks,
>
> I want to make you all aware that we will be rewriting the git history
> of tails.git, our main git repository. To make it easy for everybody and
> have less pain for us or for yourself in the future. I would like to ask
> you to push any local branches you might
Hi,
Jurre van Bergen wrote (21 Feb 2015 14:01:54 GMT) :
> I have worked on a blueprint (delete obsolete Git branches)[1] and would
> like to ask you to review it. Does the proposed workflow makes sense?
> Did I miss anything? Would you like to see anything changed and if so, why?
Looks good. Push
A minor typo fix (s/any way/anyway/)
http://repo.or.cz/tails/kytv.gitfeature/6739-electrum-typo-fix
pgpu5YtfmKGJB.pgp
Description: OpenPGP digital signature
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tail
Hi,
in the next days we're going to rewrite the Tails main Git
repository's history to get rid of old junk that makes it very large,
and thus a pain to initially clone and push for new contributors
(#6277).
A tentative timeline follows:
1. Tuesday, February 24: Tails 1.3 is out
2. By Tuesday,
The problem can be summarized by the following quote:
“By exploiting Bitcoin’s anti-DoS protection a low-resource attacker
can force users which decide to connect to the Bitcoin network through
Tor to connect exclusively through her Tor Exit nodes or to her Bitcoin
peers, totally isolating the clie
On 21/02/15 17:24, intrigeri wrote:
> Also, if you're Alan, anonym, bertagaz or sajolida, look for your name
> on that blueprint: there are a few branches I need your opinion about
> => please move them to the appropriate section.
I've deal with my section now. I had completely forgotten about the
intrigeri wrote (28 Jan 2015 16:32:57 GMT) :
> sajolida wrote (27 Jan 2015 20:31:03 GMT) :
>> We could also use the "underlay" plugin of ikiwiki to combine both Git
>> repos to have them compiled as part a single website by ikiwiki.
> Great idea! I assume it'll be a bit more work for r...@boum.org
On 19/02/15 22:38, anonym wrote:
> Hi,
>
> See the ticket for details, in particular from comment #16 and on.
> Please review and merge into devel and testing.
I withdraw this merge request. See the ticket for details.
Cheers!
___
Tails-dev mailing li
flapflap wrote (21 Feb 2015 22:14:59 GMT) :
> Please review (and maybe merge):
> https://gitorious.org/flapflap/tailsxlat.git
> branch wiki-fix-fullstop
Merged, thanks!
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/t
Alan wrote (22 Feb 2015 02:10:26 GMT) :
> * feature/edit-additional-software-conffile: this branch adds a
> subcommand to tails-additionnal software to ease creation/edition of
> its configuration. I don't remember why it never got merged.
The question is: should we keep it?
> * feature/fix_a
20 matches
Mail list logo
