From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 02:43:04 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2610816A417 for ; Sun, 19 Aug 2007 02:43:04 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mx1.freebsd.org (Postfix) with ESMTP id AB06913C442 for ; Sun, 19 Aug 2007 02:43:03 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l7J2gxLR027329; Sun, 19 Aug 2007 12:42:59 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l7J2gwcp027328; Sun, 19 Aug 2007 12:42:58 +1000 (EST) (envelope-from peter) Date: Sun, 19 Aug 2007 12:42:58 +1000 From: Peter Jeremy To: Tim Kientzle Message-ID: <20070819024258.GA23080@turion.vk2pj.dyndns.org> References: <46C79A74.9050703@kientzle.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <46C79A74.9050703@kientzle.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: "'freebsd-current@freebsd.org'" , Joerg Sonnenberger Subject: Re: RFC: #mtree signature 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: Sun, 19 Aug 2007 02:43:04 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Aug-18 18:18:44 -0700, Tim Kientzle wrote: >Any concerns or thoughts about the following >patch, which simply adds "#mtree" as the first >line of every mtree file? Sounds like a good idea. I would suggest that if we're going to add a signature block, it include a version string in case we want to incompatibly change the mtree format at some future date. Maybe: "#mtree v1.0\n". --=20 Peter Jeremy --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGx64y/opHv/APuIcRAnHqAKCwFbowLdvPd7KyaR2ee77dWoXWIACaAgdg jzjKtL8c8332IR1/F0v/BXQ= =eUbY -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o--