[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Renaming files with git not all that bad?
From: |
Yuri Khan |
Subject: |
Re: Renaming files with git not all that bad? |
Date: |
Thu, 9 Dec 2021 14:28:19 +0700 |
On Thu, 9 Dec 2021 at 14:21, Tassilo Horn <tsdh@gnu.org> wrote:
> Yes, that might be. BTW, if you still have your test example: what
> happens when you squash the copy commit and the following strip-down
> commits? Is the history still intact? (I guess, no, but who knows.)
With a squash, the stripped-down copies are different enough from the
original file to not be recognized as descendants. The diff is shown
as a single file deletion and creation of three new files.
For ancestry detection to work 100% reliably, the descendant file must
have exactly the same hash as the ancestor file, recorded in a commit.
- Renaming files with git not all that bad?, (continued)
- Re: Renaming files with git not all that bad?, Yuri Khan, 2021/12/09
- Re: Renaming files with git not all that bad?, Stefan Kangas, 2021/12/09
- Re: Renaming files with git not all that bad?, Tassilo Horn, 2021/12/10
- Re: Renaming files with git not all that bad?, Yuri Khan, 2021/12/11
- Re: Renaming files with git not all that bad?, Stefan Kangas, 2021/12/09
- Re: Renaming files with git not all that bad?, tomas, 2021/12/09
- Re: Renaming files with git not all that bad?, Stefan Kangas, 2021/12/09
- Re: Renaming files with git not all that bad?, tomas, 2021/12/10