From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 11:23:10 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB8251065672; Fri, 30 Jan 2009 11:23:10 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.freebsd.org (Postfix) with ESMTP id 4E00F8FC12; Fri, 30 Jan 2009 11:23:10 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-216-167.belrs3.nsw.optusnet.com.au [122.106.216.167]) by mail14.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n0UBN7Rw024704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Jan 2009 22:23:08 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id n0UBN7AZ064869; Fri, 30 Jan 2009 22:23:07 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id n0UBN729064868; Fri, 30 Jan 2009 22:23:07 +1100 (EST) (envelope-from peter) Date: Fri, 30 Jan 2009 22:23:07 +1100 From: Peter Jeremy To: Maxim Sobolev Message-ID: <20090130112307.GJ1755@server.vk2pj.dyndns.org> References: <49829D49.10306@freebsd.org> <4982CBC7.5050102@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eNMatiwYGLtwo1cJ" Content-Disposition: inline In-Reply-To: <4982CBC7.5050102@FreeBSD.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Tim Kientzle , "'current@FreeBSD.org'" Subject: Re: RFC: Change mtree nsec handling? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2009 11:23:11 -0000 --eNMatiwYGLtwo1cJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2009-Jan-30 01:43:35 -0800, Maxim Sobolev wrote: >Tim Kientzle wrote: >> For example, a timestamp of 1233295862.000001 >> (1233295682 seconds and 1000 nanoseconds) >> will be printed like this by mtree: >> time=3D1233295862.1000 >> Unsurprisingly, the mtree parsing works the same >> way in reverse. > >Given the age of mtree(8) I guess there are lot of existing mtree specs=20 >out there who rely on this behavior. The existing code to read nanoseconds will handle either the old format or a %09d format (the for() loop that Tim added is unnecessary) so existing specs won't have a problem. I think adding leading zeroes is the correct way to proceed. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --eNMatiwYGLtwo1cJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmC4xsACgkQ/opHv/APuIcABgCfTqyAKRapbqC3vxs+e+pkDEQN /Q8AoIbHHBx0qL5Cfo8saFjvRD464XVO =4WKO -----END PGP SIGNATURE----- --eNMatiwYGLtwo1cJ--