Re: ELPA git repo contains zero-padded file modes and running ~$ make fails

[Omar Antolín Camarena]

> For example you will create commit 2b2e62af001312a9b97724855855dfec51b5bec6 
> on Oct 13, 2065.

Correct. I have no idea how that happened either! And I don't know how to keep 
from happening again. Maybe I'm more prone to the issue because I commit from 
WSL on Windows and from a VM or Chroot on ChromeOS: I usually have the "outer" 
Windows or ChromeOS clock visible, but I usually have no idea what time the 
"inner" Linux environment thinks it is. But still: 1970, 2065? How did that 
happen and why does it only happen occasionally? But prevention of further 
instances is not as important as fixing the current problem:

Stefan Monnier mentioned rebasing but I'm unclear on what I am supposed to 
rebase on what (and I'm also unclear on how that would help: wouldn't the weird 
commit still be present?). I'll gladly do whatever is necessary to fix the 
embark repository now, I just don't understand what exactly Stefan proposes I 
do.

-- 
Omar