Bug#65933: Setting clock to UTC sometimes doesn't work

To: Taketoshi Sano <kgh12351@nifty.ne.jp>
Cc: 65933@bugs.debian.org
Subject: Bug#65933: Setting clock to UTC sometimes doesn't work
From: Adam Di Carlo <adam@onshore.com>
Date: 25 Jun 2000 16:38:31 -0400
Message-id: <[🔎] oapup53394.fsf@arroz.fake>
Reply-to: Adam Di Carlo <adam@onshore.com>, 65933@bugs.debian.org
In-reply-to: Taketoshi Sano's message of "Thu, 22 Jun 2000 17:52:44 +0900"
References: <[🔎] 394F01E7.227BFBC5@iname.com> <[🔎] 20000622175244H.kgh12351@kgh12351.nifty.ne.jp>

As a point of protocol, please do not set severity to "fixed" for CVS
fixes; rather, make an entry in debian/changelog and use (closes:
Bug#XXXX).

-- 
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>

Reply to:

Follow-Ups:
- protocol for bug fix in cvs (Re: Bug#65933: Setting clock to UTC sometimes doesn't work)
  - From: Taketoshi Sano <kgh12351@nifty.ne.jp>

References:
- Bug#65933: Setting clock to UTC sometimes doesn't work
  - From: Niccolo Rigacci <rigacci@iname.com>
- Bug#65933: Setting clock to UTC sometimes doesn't work
  - From: Taketoshi Sano <kgh12351@nifty.ne.jp>

Prev by Date: Bug#65431: Thinkpad 365x problem fixed
Next by Date: Bug#66009: marked as done (32 Mb, but "Sorry, not enough memory" (caused by new kernels sysinfo syscall))
Previous by thread: Processed: Re: Bug#65933: Setting clock to UTC sometimes doesn't work
Next by thread: protocol for bug fix in cvs (Re: Bug#65933: Setting clock to UTC sometimes doesn't work)
Index(es):
- Date
- Thread