From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-83675-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id 670F81382C5
	for <garchives@archives.gentoo.org>; Sun, 28 Jan 2018 16:07:33 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 703ACE0D96;
	Sun, 28 Jan 2018 16:07:27 +0000 (UTC)
Received: from blaine.gmane.org (unknown [195.159.176.226])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 0E5A2E0D88
	for <gentoo-dev@lists.gentoo.org>; Sun, 28 Jan 2018 16:07:25 +0000 (UTC)
Received: from list by blaine.gmane.org with local (Exim 4.84_2)
	(envelope-from <lnx-gentoo-dev@m.gmane.org>)
	id 1efpS4-0006oR-E5
	for gentoo-dev@lists.gentoo.org; Sun, 28 Jan 2018 17:05:04 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: gentoo-dev@lists.gentoo.org
From: Duncan <1i5t5.duncan@cox.net>
Subject: [gentoo-dev] Re: [News item review] Portage rsync tree verification (v4)
Date: Sun, 28 Jan 2018 16:00:49 +0000 (UTC)
Message-ID: <pan$69f55$c8eeef8c$b1fa5a8f$b0846234@cox.net>
References: <1516874667.1833.4.camel@gentoo.org>
	<1517129917.1270.1.camel@gentoo.org>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Complaints-To: usenet@blaine.gmane.org
User-Agent: Pan/0.145 (Duplicitous mercenary valetism; 27bc4e90f)
X-Archives-Salt: 0d108020-8172-4ffe-9bfb-b0f9860eee90
X-Archives-Hash: aeb182b199e9419921a8491ae3f5483b

Michał Górny posted on Sun, 28 Jan 2018 09:58:37 +0100 as excerpted:

> The new verification is intended for users who are syncing via rsync.
> Verification mechanisms for other methods of sync will be provided in
> the future.
> 
> This does not affect users syncing using git and other methods.
> Appropriate verification mechanisms for them will be provided in the
> future.


Sorry I didn't catch this sooner.  Now we have a repeat.  Maybe combine 
the two paragraphs like this:

The new verification is intended for users who are syncing via rsync.  
Users syncing using git or other methods are not affected, and 
verification for them will be provided in the future.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman