From owner-svn-src-head@freebsd.org Tue May 1 18:44:22 2018 Return-Path: Delivered-To: svn-src-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 614FFFB3B08; Tue, 1 May 2018 18:44:22 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EF6906D618; Tue, 1 May 2018 18:44:21 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1fDaGB-000FyQ-5c; Tue, 01 May 2018 21:44:19 +0300 Date: Tue, 1 May 2018 21:44:19 +0300 From: Slawa Olhovchenkov To: Ed Maste Cc: src-committers , svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r333133 - head/usr.sbin/pwd_mkdb Message-ID: <20180501184419.GV4305@zxy.spb.ru> References: <201805010053.w410rkGi046226@repo.freebsd.org> <20180501130108.GC80496@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 May 2018 18:44:22 -0000 On Tue, May 01, 2018 at 02:18:52PM -0400, Ed Maste wrote: > On 1 May 2018 at 09:01, Slawa Olhovchenkov wrote: > > On Tue, May 01, 2018 at 12:53:46AM +0000, Ed Maste wrote: > > > >> Author: emaste > >> Date: Tue May 1 00:53:46 2018 > >> New Revision: 333133 > >> URL: https://svnweb.freebsd.org/changeset/base/333133 > >> > >> Log: > >> pwd_mkdb: retire legacy v3 db support (-l option) > >> > > May be good idea to check db version before install new binary? > > Perhaps "v3 db" is too brief shorthand: it's not that the database as > a whole is v3/v4, but that it contains records of one or both types. > For 15 years we've been emitting v4 and consuming v4 records. 15 years is not aged, I am not sure about some of my databases.