[Tails-dev] Review and merge doc/8480-skip-obsolete

[sajolida]

Ticket: https://labs.riseup.net/code/issues/8480
Document how to skip /tails/obsolete for mirror operators
Branch: doc/8480-skip-obsolete into master

-- 
sajolida
___
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.

Re: [Tails-dev] Git/Redmine integration: fixing a regression with new goodies?

[intrigeri]

sajolida wrote (24 Dec 2014 17:43:28 GMT) :
> intrigeri:
>> Alan wrote (06 Dec 2014 17:11:05 GMT) :
>>> intrigeri wrote:
 So, if you folks are happy enough with that, I can encode this into
 [[contribute/*]] (merge policy, Redmine doc, whatever).
>> 
>> Now done in doc/8388-redmine-git-integration => assigned to sajolida.

> It looks good.

> I added two examples in commit 863d3cc.

Thanks! I've improved one of these in 544dac8.

> I'm also wondering about the sentence "This keyword (Will-fix) should be
> used only in topic branches, or when committing directly in the master
> branch."

> In which cases does this *not* apply? When merging topic branches into
> devel or stable, right? And you should use "Fix-committed" instead?

Right.

> Then what about explain what should be done on top of explaining what
> should not be done (be affirmative). See bcb38c1.

Fine with me.

> If you're fine with my additions, then you can merge it yourself into
> master.

Done. Thanks!

Cheers,
-- 
intrigeri
___
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.

Re: [Tails-dev] Git/Redmine integration: fixing a regression with new goodies?

[sajolida]

intrigeri:
> Alan wrote (06 Dec 2014 17:11:05 GMT) :
>> intrigeri wrote:
>>> So, if you folks are happy enough with that, I can encode this into
>>> [[contribute/*]] (merge policy, Redmine doc, whatever).
> 
> Now done in doc/8388-redmine-git-integration => assigned to sajolida.

It looks good.

I added two examples in commit 863d3cc.

I'm also wondering about the sentence "This keyword (Will-fix) should be
used only in topic branches, or when committing directly in the master
branch."

In which cases does this *not* apply? When merging topic branches into
devel or stable, right? And you should use "Fix-committed" instead?

Then what about explain what should be done on top of explaining what
should not be done (be affirmative). See bcb38c1.

If you're fine with my additions, then you can merge it yourself into
master.

-- 
sajolida
___
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.

Re: [Tails-dev] [review'n'merge:1.3] bugfix/8470-clean-up-apt-pinning

[Alan]

> this branch removes obsolete APT pinning config for XUL extensions
> we're now taking from the Tor Browser tarball, instead of from Debian.
> 
Merged thanks!
___
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.

Re: [Tails-dev] Please review bugfix/8071-Do-not-suspend-to-RAM-when-closing-lid

[intrigeri]

Hi,

matsa wrote (24 Dec 2014 05:32:33 GMT) :
> please review the following branch, which aim to fix the bug #8071:
> matsa/bugfix/8071-Do-not-suspend-to-RAM-when-closing-lid

Mangled the ticket as needed => candidate for 1.2.3.

Next time, please read "How to submit your changes" on
https://tails.boum.org/contribute/merge_policy/#index2h1, and follow
its instructions :)

Cheers,
-- 
intrigeri
___
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.

Re: [Tails-dev] [review'n'merge:1.3] feature/6880-torsocks-2, aka. drop Polipo and install torsocks 2.0

[intrigeri]

Hi,

Alan wrote (23 Dec 2014 16:45:22 GMT) :
> I checked the diff and tested wget, APT, Totem and GnuPG that all
> work fine under experimental. Tickets and design doc liiks fine too.

Cool, thanks for the review!

Please test the branch once merged into devel before pushing the final
merge, as various unrelated stuff has started accumulating
in experimental.

> The only issue blocking the merge are useless unset lines in wget
> wrapper: [...]

Answered on the ticket, reassigned to you.

[Please don't start the very same discussion in two places at the same
time, it becomes really confusing as soon as someone replies in one
place, and someone (possibly else) replies in the other. Thanks!]

Woohoo, Polipo going away :)

Cheers,
-- 
intrigeri
___
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.

[Tails-dev] Jenkins build is back to normal : build_Tails_ISO_devel #752

[tails-sysadmins]

See 

___
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.

Re: [Tails-dev] Meeting: our Tails/Jessie progress and plans

[intrigeri]

Alan wrote (23 Dec 2014 11:54:27 GMT) :
> That should work for me and this time is clearly written in my agenda.
> However I missed the time. 8:30PM CET?

OK. January 16, 8:30pm CET.

Cheers,
-- 
intrigeri
___
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.