: > WTF happened here????
: >
: > 1) Did we lose anything ?
: > ... IIUC we only lost one commit (which Noble did again?)
:
: IIUIC the only way to be sure is to compare the history from someone’s
: local repo that still hasn’t been updated with the (possibly) truncated
: history from GitHub.
Assuming we trust the commit emails, I think only 1 commit was lost, and
it looks like it was nobles ...
...
smiley (e51e50e55 -> a607a2c6c) # A6...
noble (a607a2c6c -> 84a7470f4)
noble (84a7470f4 -> a607a2c6c) FORCED BACK TO 'A6...'
noble (a607a2c6c -> dea29d12f)
jpountz (dea29d12f -> 780690b1e)
...
...so maybe this was intentional to fix a mistake?
still seems like a risky fucking thing to allow in our repo...
: > 2) I thought the main apache repo was configured to reject forced
: > pushes????
:
: THIS ^^^ apparently it isn’t. INFRA-13613.
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
