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=-5.6 required=3.0 tests=BAYES_00, 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 C9C6C2022C for ; Sat, 5 Nov 2016 15:18:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755334AbcKEPSq (ORCPT ); Sat, 5 Nov 2016 11:18:46 -0400 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:40378 "EHLO relay4-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755158AbcKEPSq (ORCPT ); Sat, 5 Nov 2016 11:18:46 -0400 Received: from mfilter49-d.gandi.net (mfilter49-d.gandi.net [217.70.178.180]) by relay4-d.mail.gandi.net (Postfix) with ESMTP id 3C70B1720AC; Sat, 5 Nov 2016 16:18:43 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mfilter49-d.gandi.net Received: from relay4-d.mail.gandi.net ([IPv6:::ffff:217.70.183.196]) by mfilter49-d.gandi.net (mfilter49-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id k9nbxSRInrDU; Sat, 5 Nov 2016 16:18:41 +0100 (CET) X-Originating-IP: 205.159.154.82 Received: from x (unknown [205.159.154.82]) (Authenticated sender: josh@joshtriplett.org) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id A1CE6172093; Sat, 5 Nov 2016 16:18:39 +0100 (CET) Date: Sat, 5 Nov 2016 09:18:36 -0600 From: Josh Triplett To: Christian Couder Cc: Junio C Hamano , git , "Shawn O. Pierce" , Jeff King , Nguyen Thai Ngoc Duy Subject: Re: Regarding "git log" on "git series" metadata Message-ID: <20161105151836.wztypzrdywyltvrc@x> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20161014 (1.7.1) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Sat, Nov 05, 2016 at 01:45:27PM +0100, Christian Couder wrote: > And with what Peff says above it looks like we will need ways > configure and tweak commit reachability with gitlink/gitref anyway. So > the point of gitref compared to gitlink would be that they just have a > different reachability by default. But couldn't that be replaced by a > default rule saying that when a gitlink is reached "this way or that > way" then the commit reachability should be enforced, and otherwise it > should not be? Any version of git unaware of that rule, though, would consider objects only reachable by gitlink as unreachable and delete them, causing data loss. Likewise for a server not aware of that rule. And a server unaware of that rule would not supply those objects to a client pulling such a branch. So I don't think "gitlink defined as reachable" quite works, unless we make some other format-incompatible change that forces clients and servers touching that gitlink to know about that reachability rule. (In the absence of a hack such as making the same commit a parent.)