On Tue, Nov 21, 2017 at 12:00 AM, Elijah Newren <new...@gmail.com> wrote: > This patchset introduces directory rename detection to merge-recursive; I'm > resubmitting just a few hours after my PATCHv2 because I didn't know about > the DEVELOPER=1 flag previously, and my code had a number of > warnings/errors. I would have just submitted fixup/squash patches, but > when I checked, there sadly they cause merge conflicts when rebasing > > See https://public-inbox.org/git/20171110190550.27059-1-new...@gmail.com/ > for the first series, design considerations, etc, and > https://public-inbox.org/git/20171120220209.15111-1-new...@gmail.com/ for > v2.
Thanks, I'll take a look! Protip: To make it easy for reviewers add an interdiff[1] between the different versions of the patch series, this can be done via tbdiff[2] for example, or in case you still have the old branch around or Junio has it queued already, you can do a diff against that branch. I just looked through recent cover letters and it doesn't seem to be common (any more?), or just not suitable for the series currently in flight. [1] for example https://public-inbox.org/git/20171116020039.17810-1-sbel...@google.com/ [2] https://github.com/trast/tbdiff Stefan
