Anonymous commit (empty Author and Committer)
Quoted 23 lines
30.10.2015 23:59, Lennart Sorensen пишет:
Quoted 21 lines · Vladimir 'φ-coder/phcoder' Serbinenko
Quoted 19 lines · Vladimir 'φ-coder/phcoder' Serbinenko
Quoted 8 lines · Vladimir 'φ-coder/phcoder' Serbinenko
Quoted 6 lines · Andrei Borzenkov
Quoted 6 lines
Quoted 6 lines
Quoted 4 lines
I was not even aware that this is possible. Is there anything on server side that can prevent it?
Would be good if commit were amended and force pushed to fix it.
It is a bug in SGit. I'll investigate how it happened
I don't have non-fast-forward rights. Does someone from savannah-users have them? Could he just delete this commit?
Quoted 6 lines
Quoted 2 lines
If you do that, then anyone that already did a pull after it went in will have a broken tree. Rather annoying.
If we decide to fix this commit it is better done now, while it is the last one. It is annoying but do you have suggestion how it can be done differently?
+1 to undo it now
Indeed. The faster it is fixed smaller the number of potential unintentional repeats for it, if any.