From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 63256 invoked by alias); 11 Dec 2019 23:00:46 -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 63150 invoked by uid 89); 11 Dec 2019 23:00:38 -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=heuristics X-HELO: mail-ot1-f54.google.com Received: from mail-ot1-f54.google.com (HELO mail-ot1-f54.google.com) (209.85.210.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 11 Dec 2019 23:00:25 +0000 Received: by mail-ot1-f54.google.com with SMTP id 66so338451otd.9 for ; Wed, 11 Dec 2019 15:00:18 -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=VYPuRBe4W7qCXGDk3Zuxxz4Fd8KFQDbVTva3VUxwajM=; b=WS4V9dVdoppGrlsEGV+s1Im2GM801h2zszXFpdJg9j4B8PkG32yyltygzS/II0gYvH gOIQ1DHfbS1CijTtsfVhB7awt87ZKl1K93XUQCwEXK8X/UpW5Olq1b71F5lkdO3uqRZJ mqFoyhYN39LKh45mKroU6KpoL4aiXxYvIjOKaWVj/ylDiAScIJLAQf3+la9cfCkUZkJE gHj5NInaRYXeusTGF+sF6m2xbm4lIEtCbOlmpzQJ4s1NiqDQIfAVTfgjZquotKJz+Q5i 9KBhSbbmR1x3YXBtT1Pf128FTa252JgR31cJ+SdaX4bp6A8BileCwUQZk9ewQys/L3zq jQgA== MIME-Version: 1.0 References: <838snjbkqm.fsf@gnu.org> In-Reply-To: <838snjbkqm.fsf@gnu.org> From: "Christian Biesinger via gdb" Reply-To: Christian Biesinger Date: Wed, 11 Dec 2019 23:00: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/msg00011.txt.bz2 On Tue, Dec 10, 2019 at 10:32 PM Eli Zaretskii wrote: > > > From: "Christian Biesinger via gdb" > > Date: Tue, 10 Dec 2019 17:18:58 -0500 > > > > On IRC it was mentioned that git may have issues with renames like > > that but I have found that "git log --follow" and such are doing a > > good job with that, at least as long as the same commit doesn't change > > the file too much while it is renamed, which I wouldn't expect to be a > > problem here. > > 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. > 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. Christian