From owner-freebsd-bugs  Thu Jun  7 19: 7:40 2001
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.aist.go.jp (mx1.aist.go.jp [150.29.246.133])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5756B37B401; Thu,  7 Jun 2001 19:07:37 -0700 (PDT)
	(envelope-from akr@m17n.org)
Received: from rpsmtp1.aist.go.jp
	by mx1.aist.go.jp  with ESMTP id f5827V519199;
	Fri, 8 Jun 2001 11:07:31 +0900 (JST)
	env-from (akr@m17n.org)
Received: from eccu1-1.etl.go.jp
        by rpsmtp1.aist.go.jp  with ESMTP id f5827VQ24098;
        Fri, 8 Jun 2001 11:07:31 +0900 (JST)
        env-from (akr@m17n.org)
Received: from flux.etl.go.jp (dhcpea003 [150.29.203.193])
	by eccu1-1.etl.go.jp (8.11.4/8.11.4) with ESMTP id f5827U123189;
	Fri, 8 Jun 2001 11:07:30 +0900 (JST)
Received: by flux.etl.go.jp (Postfix, from userid 23483)
	id C1049728; Fri,  8 Jun 2001 11:07:29 +0900 (JST)
To: wollman@FreeBSD.org
Cc: freebsd-bugs@FreeBSD.org
Subject: Re: bin/27630: mktime failure.
References: <200106052049.f55KnIX35198@freefall.freebsd.org>
MIME-Version: 1.0 (generated by SEMI 1.14.0 - "Iburihashi")
Content-Type: text/plain; charset=US-ASCII
From: Tanaka Akira <akr@m17n.org>
Date: 08 Jun 2001 11:07:28 +0900
In-Reply-To: <200106052049.f55KnIX35198@freefall.freebsd.org>
 (wollman@FreeBSD.org's message of "Tue, 5 Jun 2001 13:49:18 -0700 (PDT)")
Message-ID: <hvohexr207z.fsf@flux.etl.go.jp>
Lines: 13
User-Agent: T-gnus/6.14.5 (based on Gnus v5.8.7) (revision 08) SEMI/1.14.0 (Iburihashi) Deisui/1.14.0 (Kikuhime) APEL/10.2 Emacs/21.0.103 (i386-unknown-freebsd4.2) MULE/5.0 (SAKAKI)
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

In article <200106052049.f55KnIX35198@freefall.freebsd.org>,
  wollman@FreeBSD.org writes:

> A fix from the maintainer was committed to current.  Does this fix resolve
> your problem?

Since I don't have FreeBSD-current environment, I cannot check the
problem on FreeBSD-current.  But I tried tzcode2001c with the patch in
<A4EC106C46EDF94A8D60B03E984183979BB498@nihexchange2.nih.gov> which is
commited to current.  It works fine.  So I believe FreeBSD-current fix
the problem.
-- 
Tanaka Akira

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message