[llvm-dev] RFC: Move the test-suite LLVM project to GitHub?

Joachim Durchholz via llvm-dev llvm-dev at lists.llvm.org
Thu Feb 25 00:07:35 PST 2016

Am 25.02.2016 um 08:16 schrieb Chandler Carruth via llvm-dev:
> Yep. I have no idea what the correct process is here.

Don't worry, git never destroys data :-)

Fine print:

Yes git can destroy data, but not in the way you think.

Inadvertent data loss can happen in your workdir. Do a "git stash" or 
"git commit" before starting with a rebase or merge, and nothing bad can 

Also, if you get confused during merge or rebase (and that can easily 
happen if you try to do too many things at once), your history as seen 
in "git log" may start to miss important points in history. It's easy to 
get into this state via "git reset", i.e. when you started to clean up 
things and git did something that you did not expect it to do.
However, "git log" is incomplete; it just shows those part of history 
that lead to a branch tip. You get the full log via "git reflog", and 
you can reference the unnamed tips via their hash, so you can always 
reset the branches to those hashes that you want resurrected.
There are two ways how unnamed tips can get lost: "git purge", so don't 
do this; and by letting unnamed tips get automatically purged after 30 
days of inactivity, but nobody lets a messed-up history live that long 
and push it to a public repo.

If if it comes to the worst, you messed up the repo and pushed it to the 
public site: *somebody* will still have a clean copy of the repo sitting 
on his disk, and you can upload that and reset to that last known good 


More information about the llvm-dev mailing list