30.10.2015 23:19, Vladimir 'φ-coder/phcoder' Serbinenko пишет:
On 30.10.2015 21:09, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
On 30.10.2015 21:06, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
On 30.10.2015 15:26, Andrei Borzenkov wrote:
See
http://git.savannah.gnu.org/cgit/grub.git/commit
31.10.2015 10:02, Andreas Schwab пишет:
Kaz Kylheku writes:
Nope. They will have a git in which that commit looks like their own
local work. *Someone* will inadvertently do a "git push" to blast out
their changes based on that deleted commit, thereby causing it to
reappear.
30.10.2015 23:59, Lennart Sorensen пишет:
On Fri, Oct 30, 2015 at 09:19:19PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko
wrote:
On 30.10.2015 21:09, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
On 30.10.2015 21:06, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
On 30.10.2015 15:26, Andrei
See
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=206676601eb853fc319df14cd3398fbdfde665ac
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.
--
To unsubscribe from this
4 matches
Mail list logo