[Tails-dev] time-sync commits cherry-pick to stable branch?

Delete this message

Reply to this message
Author: intrigeri
Date:  
To: tails-dev
Subject: [Tails-dev] time-sync commits cherry-pick to stable branch?
Hi,

I'm working on fixing some parts of our time sync' system right now,
in a branch forked from stable as proposed earlier, and I realize some
bugfixes in this area were applied to devel but are not part of
stable; the following commits look like good candidates for
cherry-picking to me. Thoughts? (I'd especially welcome a "Go" from
anonym, their original author).


commit 5cf9ba4cf43278c0aa6fe34de77f816103fa56b5
Author: Tails developers <amnesia@???>
Date: Thu Jan 5 11:49:48 2012 +0100

    Import new htpdate (at commit 45dbc4c).


    This adds the -D option we need.


commit e632575403622d40cb423129052d45556cbd28f5
Author: Tails developers <amnesia@???>
Date: Thu Jan 5 11:58:39 2012 +0100

    Simplify how the notification detects when htpdate exits.


commit 23e52507822816ee2b914fea3b85c5408f543cb9
Author: Tails developers <amnesia@???>
Date: Thu Jan 5 12:07:49 2012 +0100

    Make I2P wait for htpdate to finish in order to avoid time jumps.


commit 17cf7f43ea2abc438dbaf370707267353e4ff1de
Author: Tails developers <amnesia@???>
Date: Thu Jan 5 12:36:12 2012 +0100

    Fixup of the previous two commits (they were pushed prematurely).



Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
| If you must label the absolute, use it's proper name: Temporary.