[llvm-dev] How to deal with accidental directory tree deletes, downstream?

Jeremy Lakeman via llvm-dev llvm-dev at lists.llvm.org
Wed Apr 17 23:30:51 PDT 2019

I'm pretty sure you could use 'git rebase' then 'git replace' to graft an
alternate history over that patch of commits. Perform your merges, then
optionally remove the replacements?

On Wed, 17 Apr 2019 at 22:05, via llvm-dev <llvm-dev at lists.llvm.org> wrote:

> Hello fellow downstream residents,
> I see that r358546 accidentally deleted an entire subtree, which was
> reverted in r358552.  This of course caused a big merge conflict in
> our local repo, and internally we've been debating tactics for dealing
> with it, hopefully without losing our original history.
> Has anyone else handled this in a way that they are happy with?  We
> found a StackOverflow post that is potentially helpful:
> https://stackoverflow.com/questions/44990103/how-to-undelete-file-in-git-and-keep-his-original-blame-history
> Doing this on our local copy of the upstream repo means we would not
> have an exact copy anymore, which seems like a Bad Idea.
> Is there a smooth way to resolve the merge conflict that does *not*
> delete our local tree? I suppose we can somehow not accept the
> accidental deletes, and then when we run forward to r358552 it will
> decide we already have those files and it will Just Work?
> Tips and hints welcome.
> Thanks,
> --paulr
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190418/0ff4d796/attachment.html>

More information about the llvm-dev mailing list