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=-4.2 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI 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 0F298211B3 for ; Thu, 13 Dec 2018 06:25:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726641AbeLMGZJ (ORCPT ); Thu, 13 Dec 2018 01:25:09 -0500 Received: from bsmtp7.bon.at ([213.33.87.19]:64945 "EHLO bsmtp7.bon.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726542AbeLMGZI (ORCPT ); Thu, 13 Dec 2018 01:25:08 -0500 Received: from dx.site (unknown [93.83.142.38]) by bsmtp7.bon.at (Postfix) with ESMTPSA id 43FkDy4d2mz5tl9; Thu, 13 Dec 2018 07:25:06 +0100 (CET) Received: from [IPv6:::1] (localhost [IPv6:::1]) by dx.site (Postfix) with ESMTP id 0F4EFE2; Thu, 13 Dec 2018 07:25:06 +0100 (CET) Subject: Re: [PATCH 2/2] mingw: allow absolute paths without drive prefix To: Junio C Hamano Cc: Johannes Schindelin , Johannes Schindelin via GitGitGadget , git@vger.kernel.org References: <50ac31ef7f4380f37a0e2d3b75e82b324afee9e3.1544467631.git.gitgitgadget@gmail.com> <11b17e5d-e843-463b-77da-263e8e3b7598@kdbg.org> <8a484f86-1d43-fc0a-22b4-39c770cda6cb@kdbg.org> From: Johannes Sixt Message-ID: <8efe7938-12a9-7db3-8f95-825ee2e32247@kdbg.org> Date: Thu, 13 Dec 2018 07:25:05 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Am 13.12.18 um 03:48 schrieb Junio C Hamano: > So,... what's the conclusion? The patch in the context of my tree > would be a no-op, and we'd need a prerequisite change to the support > function to accompany this patch to be effective? Correct, that is my conclusion. -- Hannes