From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_NONE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id B1A821F463 for ; Mon, 9 Dec 2019 22:50:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727291AbfLIWuc convert rfc822-to-8bit (ORCPT ); Mon, 9 Dec 2019 17:50:32 -0500 Received: from mail-wm1-f65.google.com ([209.85.128.65]:51760 "EHLO mail-wm1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726230AbfLIWua (ORCPT ); Mon, 9 Dec 2019 17:50:30 -0500 Received: by mail-wm1-f65.google.com with SMTP id g206so1113157wme.1 for ; Mon, 09 Dec 2019 14:50:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=h4qZZBd3EM8yBizXqLLIVxaabh+ANMLKnYkRrtQ7GM0=; b=hPBR21+Ek46oXeUkfR9VFuoIorIycP4hu5Pu1Cmlo4328ZLatrx1ulb6lmWQH6eBzf kZ+A9DQpGTeO/v9yWGeKvfb0CADHFpKeO1ec/gus1l3mWG4tkhEkfsIePGjTCRdeRrAL LOD96htRmtKeyB4SHnj5C77ZwdVKsGfuGSB3BUmIRuHqFxIFb51KqW/+lP9Pyl7EvK8K laulOScTTSDZIcVaDwecK8TA0JGhuJD1GhTJ0oNzd0Kkoh9LSeTMcWk/lCgCOnn2jMDl AyjzT0MUCm9FIah6FND8kXo/hiZmyr2Y+a6LhWlEy45iIaq2BS7AfVJMhCiBYGNT3Dcr Nrvw== X-Gm-Message-State: APjAAAVr91aQIE0hgkXjQBh2ukBU+u5ByvXZ02iuuJmkH7NEnbJ8wpxA Nvzz5bMw9+f35NkoOvL75AJQHpvO+Tk1s34jgnE= X-Google-Smtp-Source: APXvYqy7hLJUGcNhLuYjEjbcCSyfrmZDL2RgiebXM5EwUWr9V6Fr9D4WQ/ODsef+fHEJ/57fU70YTedljSm7qEqjHtk= X-Received: by 2002:a1c:1b88:: with SMTP id b130mr1419387wmb.4.1575931828402; Mon, 09 Dec 2019 14:50:28 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Eric Sunshine Date: Mon, 9 Dec 2019 17:50:17 -0500 Message-ID: Subject: Re: [PATCH v2 1/1] "git lfs" allows users to specify the custom storage location by configuration variable lfs.storage, but when "git p4" interacts with GitLFS pointers, it always used the hardcoded default that is the .git/lfs/ directory, without paying attention to the configuration. To: Junio C Hamano Cc: panzercheg via GitGitGadget , Git List , panzercheg , Johannes Schindelin Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Mon, Dec 9, 2019 at 5:27 PM Junio C Hamano wrote: > >Subject: Re: [PATCH v2 1/1] "git lfs" allows users to specify the custom storage location by configuration variable lfs.storage, but when "git p4" interacts with GitLFS pointers, it always used the hardcoded default that is the .git/lfs/ directory, without paying attention to the configuration. > > Oops, what happened here? > > I wonder/I wish if GGG can be a bit more helpful when seeing a > commit that looks "strange". There is an open issue[1] regarding that. [1]: https://github.com/gitgitgadget/gitgitgadget/issues/120