Perfect! Thanks for your suggestion, Steve. That does sound like a
cleaner solution than what I had proposed.
Roddy
On Mon, Feb 29, 2016 at 5:28 PM Steve McIntyre wrote:
> Hi Roddy, and thanks for getting in touch!
>
> On Wed, Feb 24, 2016 at 09:27:26PM +, Roddy Shuler wrote:
> >Package:
Hi Roddy, and thanks for getting in touch!
On Wed, Feb 24, 2016 at 09:27:26PM +, Roddy Shuler wrote:
>Package: fake-hwclock
>Version: 0.9
>
>Upon first use of fake-hwclock, if the device does not have a
>battery-backed clock (and has not saved fake-hwclock.data yet), the clock
>will typically
Package: fake-hwclock
Version: 0.9
Upon first use of fake-hwclock, if the device does not have a
battery-backed clock (and has not saved fake-hwclock.data yet), the clock
will typically start at Jan 1, 1970 UTC. This has the following
repercussions:
- Before manually adjusting the time, it will b
3 matches
Mail list logo