Hi !
this patch correct a missplet word and add the 'how do I ping' question in
faq.mdwn, and it add a word adout Gigabyte motherboards in the known issues.
cheers.
From d7fc120040346d691024533982b9efd3312e7c02 Mon Sep 17 00:00:00 2001
From: Debian Live user amnesia@localhost.localdomain
Date:
Hi,
first of all, let me state that I'm delighted to see more
contributions to the FAQ and known issues coming from frontdesk
recently. Great job!
goupille wrote (03 Jun 2015 20:27:40 GMT) :
this patch correct a missplet word
I applied this one, thanks!
and add the 'how do I ping' question
On 06/03/2015 12:26 PM, intrigeri wrote:
anonym wrote (31 May 2015 22:20:13 GMT) :
* 2.0 = Tails_maintainability
* 3.0 = Tails_hardening
* 4.0 = Tails_jessie
Yay, I like it!
Note that strictly speaking, we don't need the Tails_ prefix. Also,
I would find it nice to clearly distinguish
Hi,
sajolida wrote (01 Jun 2015 11:31:18 GMT) :
anonym:
I feel more aligned with anonym's position.
Works for me too :)
Do we need to have a constant number of positions in the version
number scheme for technical reasons?
I don't think so.
Couldn't we add an extra number only when we do
On 06/03/2015 12:38 PM, intrigeri wrote:
sajolida wrote (01 Jun 2015 11:31:18 GMT) :
anonym:
Couldn't we add an extra number only when we do an
emergency release?
I think we can, and we should.
Let's just be clear on that it is the action of adding an extra *last*
number for emergency
On 06/03/2015 01:51 PM, intrigeri wrote:
Hi,
anonym wrote (03 Jun 2015 11:22:31 GMT) :
On 06/03/2015 12:26 PM, intrigeri wrote:
Note that strictly speaking, we don't need the Tails_ prefix. Also,
I would find it nice to clearly distinguish the target versions that
will be 100% reached on a
anonym wrote (31 May 2015 22:20:13 GMT) :
On 05/31/2015 09:24 AM, intrigeri wrote:
* we're not very clear what the first component means (1.0 had
a well-defined meaning, no idea what 2.0 will be; we're currently
using 2.0 and 3.0 on our roadmap to make mid/long-term perspectives
and
Hi,
anonym wrote (03 Jun 2015 11:22:31 GMT) :
On 06/03/2015 12:26 PM, intrigeri wrote:
Note that strictly speaking, we don't need the Tails_ prefix. Also,
I would find it nice to clearly distinguish the target versions that
will be 100% reached on a flag day, and by releasing a given Tails
anonym:
That reason wasn't stated, but it is that I too feel it's
important to quickly be able to tell whether a release was/is/will be a
major, bugfix or emergency one.
+1!
___
Tails-dev mailing list
Tails-dev@boum.org
anonym wrote (03 Jun 2015 11:59:20 GMT) :
On 06/03/2015 12:38 PM, intrigeri wrote:
sajolida wrote (01 Jun 2015 11:31:18 GMT) :
anonym:
Couldn't we add an extra number only when we do an
emergency release?
I think we can, and we should.
Let's just be clear on that it is the action of
See https://jenkins.tails.boum.org/job/build_Tails_ISO_feature-jessie/514/
--
[...truncated 12305 lines...]
ERROR: ld.so: object '/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD
cannot be preloaded (cannot open shared object file): ignored.
ERROR:
11 matches
Mail list logo
