From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 86831 invoked by alias); 14 Dec 2019 18:20:22 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 86823 invoked by uid 89); 14 Dec 2019 18:20:22 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-17.4 required=5.0 tests=AWL,BAYES_00,ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_PASS,USER_IN_DEF_SPF_WL autolearn=ham version=3.3.1 spammy=Git's, disadvantages, gits, H*f:sk:838snjb X-HELO: mail-ot1-f67.google.com Received: from mail-ot1-f67.google.com (HELO mail-ot1-f67.google.com) (209.85.210.67) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 14 Dec 2019 18:20:21 +0000 Received: by mail-ot1-f67.google.com with SMTP id d17so3426561otc.0 for ; Sat, 14 Dec 2019 10:20:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8Vd+VCGcwZsigmWLEIDa4zYQca5FDO9aNdG42CscgiI=; b=X+EsEW7msNMuRMOl4WpRF+XLPH02m0HrvUMn4m/yREKLUb/EN3b/Qf2IkiE++XhkFg K1XoSI3+I8BpKfjkFq0L3DfOsmo5bGs1UsCcqH06hnE/eiIL11T5L1uB1ulzlRuR7JQS aRGjZutvJPuM8zUsSWWXJzJ6GHrlxRa6YD1lEWFq5OLbVjjwpJlDEbi48Lr28Rggv2sC SyVlN7oeSjidAd/xQLRXcpX9BVLD3xjI45M5oiGEblreYc5YmRVlb3vHibC7OOvmbSBw qPtAV3A7CtJqLdb/BUDTpizPaldocO5wShseSTCkH87/52vy61emCbaVjt+gwRdYoSCR qGIQ== MIME-Version: 1.0 References: <838snjbkqm.fsf@gnu.org> <838sni9ifm.fsf@gnu.org> In-Reply-To: <838sni9ifm.fsf@gnu.org> From: "Christian Biesinger via gdb" Reply-To: Christian Biesinger Date: Sat, 14 Dec 2019 18:20:00 -0000 Message-ID: Subject: Re: Renaming .c files to .cc? To: Eli Zaretskii Cc: gdb@sourceware.org, Pedro Alves Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00026.txt.bz2 On Thu, Dec 12, 2019 at 1:17 AM Eli Zaretskii wrote: > > > From: Christian Biesinger > > Date: Wed, 11 Dec 2019 17:59:39 -0500 > > Cc: gdb@sourceware.org, Pedro Alves > > > > > Not every Git command has a --follow option, so renaming files does > > > have disadvantages in that area. > > > > Do you have a specific command in mind that doesn't? I haven't come > > across that yet myself. > > Are you saying that every Git command supports that option? I don't > think so. Sorry, that's not what I meant; I had never run into one where I missed that option, and you sounded like you had one in mind, so I was curious. I don't know either way if there are git commands that miss that option. BTW, there is a setting to make --follow the default. git config --global log.follow true > And even those who do support it impose limitations when it's used. > For example, > > $ git log file1 file2 ... > > works, but > > $ git log --follow file1 file2 ... > > fails with an error message. So many important forensic > investigations limit you to single files when using --follow. OK. > > > Also, even with --follow, Git's tracking of renaming is heuristics, > > > so it can fail. > > > > Technically correct, but not an issue in practice when files are being > > renamed without changes, like they would be here. > > That's not guaranteed, because several files with similar contents can > dupe the heuristics. > > Anyway, like Pedro said: the reasons for being in the "rather not" > camp are not strong. OK, I'll drop this. Christian