From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_HI, RP_MATCHES_RCVD shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id 5A30420281 for ; Tue, 3 Oct 2017 00:52:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751247AbdJCAwY (ORCPT ); Mon, 2 Oct 2017 20:52:24 -0400 Received: from pb-smtp2.pobox.com ([64.147.108.71]:57997 "EHLO sasl.smtp.pobox.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750869AbdJCAwX (ORCPT ); Mon, 2 Oct 2017 20:52:23 -0400 Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id A00FAB3035; Mon, 2 Oct 2017 20:52:22 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=NJPsotqqobRxCdDbTBIkr6kwgDg=; b=MSs7B1 9MDTxNXMRQRCLK/SpE0fPmwfaykC/iiCAe/2IPs+eBho4m6Z3NseCJXegrAlj0du EOKJGJPePSgd1DF51qk+tphBZW7VahVFmtU6G4X8UC2cOV2YNNimdkGnavL/aMYw UmDgvSnLk9YrNgXumzsVt7YKxJ1abWsU8hJQw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=nzJqziKHMC3VjqsFJKZJXKroDqibSUuO nKxQXzkazUGzBiJciXbenY5V+nkmEcjtyVJWpuhSBKo99Z7RSaytOj9r+Z2eVuiT n3ecZ1gwCbahOtUekacfB09VPpyfTRCh3twWSsZr9E9mCMULUVqYt/cSNprUKzUe TcIvjvIOn2U= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 97B82B3034; Mon, 2 Oct 2017 20:52:22 -0400 (EDT) Received: from pobox.com (unknown [104.132.0.95]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 001A8B3033; Mon, 2 Oct 2017 20:52:21 -0400 (EDT) From: Junio C Hamano To: Jeff Hostetler Cc: Stefan Beller , Johannes Schindelin , Philip Oakley , Pavel Kretov , "git\@vger.kernel.org" Subject: Re: [idea] File history tracking hints References: <04DDB36236444FFD8C3668AA7B62B154@PhilipOakley> <5fb263a8-d83b-64a7-812f-fd8e3748feb6@jeffhostetler.com> Date: Tue, 03 Oct 2017 09:52:20 +0900 In-Reply-To: (Jeff Hostetler's message of "Mon, 2 Oct 2017 16:02:09 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: 1D608E06-A7D5-11E7-87D1-575F0C78B957-77302942!pb-smtp2.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Jeff Hostetler writes: >> How do you know when a guid needs adaption? > > I'm not sure I know what you mean by "adaption". I think he meant adapting, and I think he is referring to what I wrote in the message upthread to explain why "file ID" would not help. It seems to me, from reading the remainder of your message, that it is also becoming clear to you that "file ID" would not help and your conceptual thing was merely a hand-waving that was dubious how it could be made into a concrete working design? Hopefully we can converge on a workable design that does not involve "file ID", and that would be a good outcome.