Is http://llvm.org/git/llvm.git trunk wipped out?

Duncan P. N. Exon Smith dexonsmith at apple.com
Wed Jan 7 14:56:38 PST 2015


> On 2015-Jan-07, at 14:49, Ramkumar Ramachandra <artagnon at gmail.com> wrote:
> 
> Anton Korobeynikov wrote:
>> Most probably git pull --rebase will happily clean all the stuff.
> 
> That's simply a fetch + rebase: the rebase will try to rebase the good
> commit on top of the bad commit and fail horribly. Use the reset
> --hard I suggested.

There are no good commits after the bad commit, unless you happened to be
modifying the same file Sean was (in r225400, which somehow triggered the
bug), since all other files were deleted.

In practice `git pull --rebase` should work fine in this case.



More information about the llvm-commits mailing list