From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-47323-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 95260 invoked by alias); 11 Dec 2019 03:32:32 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
Received: (qmail 95251 invoked by uid 89); 11 Dec 2019 03:32:31 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-3.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=H*r:142, HX-Languages-Length:619
X-HELO: eggs.gnu.org
Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 11 Dec 2019 03:32:30 +0000
Received: from fencepost.gnu.org ([2001:470:142:3::e]:35998)	by eggs.gnu.org with esmtp (Exim 4.71)	(envelope-from <eliz@gnu.org>)	id 1iesjk-0001My-8Q; Tue, 10 Dec 2019 22:32:28 -0500
Received: from [176.228.60.248] (port=2188 helo=home-c4e4a596f7)	by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)	(Exim 4.82)	(envelope-from <eliz@gnu.org>)	id 1iesjj-0001Dx-KS; Tue, 10 Dec 2019 22:32:28 -0500
Date: Wed, 11 Dec 2019 03:32:00 -0000
Message-Id: <838snjbkqm.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Christian Biesinger <cbiesinger@google.com>
CC: gdb@sourceware.org, palves@redhat.com
In-reply-to:	<CAPTJ0XEXR2Kb9CU1j17g9VE9fU07xsWHJSk4QiD1ma47F1TSsA@mail.gmail.com>	(gdb@sourceware.org)
Subject: Re: Renaming .c files to .cc?
References: <CAPTJ0XEXR2Kb9CU1j17g9VE9fU07xsWHJSk4QiD1ma47F1TSsA@mail.gmail.com>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-IsSubscribed: yes
X-SW-Source: 2019-12/txt/msg00006.txt.bz2

> From: "Christian Biesinger via gdb" <gdb@sourceware.org>
> 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.

Also, even with --follow, Git's tracking of renaming is heuristics,
so it can fail.