From owner-cvs-all@FreeBSD.ORG Sun Jan 22 23:54:43 2006 Return-Path: X-Original-To: cvs-all@FreeBSD.org Delivered-To: cvs-all@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8C4A16A41F; Sun, 22 Jan 2006 23:54:43 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id A434243D5D; Sun, 22 Jan 2006 23:54:39 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from smiley (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 79B7E19F2C; Sun, 22 Jan 2006 15:54:36 -0800 (PST) From: "Darren Pilgrim" To: "'Edwin Groothuis'" Date: Sun, 22 Jan 2006 15:54:30 -0800 Message-ID: <000001c61faf$30bcdf60$672a15ac@smiley> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <200601222124.k0MLO5A9083860@repoman.freebsd.org> Importance: Normal Cc: cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: RE: "SHA256ify" commits X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jan 2006 23:54:43 -0000 There's no criticism here, just one geek's interested query. I'm already familiar with the reasons for moving to SHA256, but how is this process being accomplished? What are you using to calculate and insert the new hashes? What conditions result in the "manually checked and updated" commit? If there's previous list traffic answering these questions, by all means, point me in a direction.