From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id E68E0138B3E for ; Wed, 20 Feb 2013 13:30:14 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4EAC021C005; Wed, 20 Feb 2013 13:30:01 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4D61B21C002 for ; Wed, 20 Feb 2013 13:30:00 +0000 (UTC) Received: from [130.149.91.41] (shishapangma.kbs.tu-berlin.de [130.149.91.41]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: chithanh) by smtp.gentoo.org (Postfix) with ESMTPSA id 2EAE233DE7D for ; Wed, 20 Feb 2013 13:29:58 +0000 (UTC) Message-ID: <5124CFCC.40202@gentoo.org> Date: Wed, 20 Feb 2013 14:29:48 +0100 From: =?UTF-8?B?Q2jDrS1UaGFuaCBDaHJpc3RvcGhlciBOZ3V54buFbg==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: linux-firmware References: <1361020086.1920.51.camel@belkin4> <511F8D2E.1080006@flameeyes.eu> <511F9A9F.8040206@gentoo.org> <511F9ADE.2050503@flameeyes.eu> <20767.41371.270947.851486@a1i15.kph.uni-mainz.de> <5120654B.6050406@gentoo.org> <20768.43798.568305.561675@a1i15.kph.uni-mainz.de> <512389BF.9090504@gentoo.org> In-Reply-To: X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 2f75158b-2be4-4114-9379-a15cb5ab71a0 X-Archives-Hash: 2ff7358826ca4fbc20c9ca3eddbbcbc3 Tomáš Chvátal schrieb: > 2013/2/20 Rich Freeman : >> There is a current QA policy that anything using an scm to download >> sources cannot be stabilized, because there is no way to verify the >> manifest. >> >> I'm actually wondering if that makes sense with git when a specific >> commit is referenced, since everything is content-hashed anyway. >> Perhaps we just need to confirm that git actually checks the hash. >> > If you checkout some revision or tag just create the darn tarball > yourself as it is much cleaner solution and you don't force user to > install git or other scm tools unless they need them. Problem is that the tarball cannot be redistributed by us. Now what? Best regards, Chí-Thanh Christopher Nguyễn