Re: [PATCH v7 31/31] merge-recursive: ensure we write updates for directory-renamed file
- From
Stefan Beller <sbeller@google.com>
- Date
- Feb 5, 2018, 21:58 UTC
- Message-ID
- <CAGZ79kaZNF=Tr5jaOBqkoFhsMC9fzM3pGS1+1GEY3542xtY8=w@mail.gmail.com>
- In-Reply-To
- <20180130232533.25846-32-newren@gmail.com>
On Tue, Jan 30, 2018 at 3:25 PM, Elijah Newren <newren@gmail.com> wrote:
Show 10 quoted lines
> When a file is present in HEAD before the merge and the other side of the > merge does not modify that file, we try to avoid re-writing the file and > making it stat-dirty. However, when a file is present in HEAD before the > merge and was in a directory that was renamed by the other side of the > merge, we have to move the file to a new location and re-write it. > Update the code that checks whether we can skip the update to also work in > the presence of directory renames. > > Signed-off-by: Elijah Newren <newren@gmail.com> > ---
Now I did not just review the tests, but also the code of this series. (though I think I was more detail oriented on Friday) All patches that had no comments are fine with me, I left some comments on others.
Thanks, Stefan