Re:Git 2.0 changes push default to ‘simple’
by dilap on Saturday November 02, 2013 @01:42PM
(#6659958)
Even w/o the distributed stuff, git reflog has your back. Once something has been comitted, you have to try pretty hard to really lose it.
[ Parent
| on HN ]
Re:Git 2.0 changes push default to ‘simple’
by Anderkent on Saturday November 02, 2013 @01:58PM
(#6660029)
That's only if you have ssh access to the server. I don't think there's a way of seeing the reflog of a remote? I.e. if you're using github and the branch only lives there, can you undo an overwrite?
Re:Git 2.0 changes push default to ‘simple’
by eridius on Saturday November 02, 2013 @07:05PM
(#6661247)
If you have the output from your `git push -f` you can, because it outputs both the old and new ref for each modified branch.
Re:Git 2.0 changes push default to ‘simple’
by dilap on Saturday November 02, 2013 @02:54PM
(#6660246)
Oh, interesting, I think you're right. That's a bit unfortunate actually!
Re:Git 2.0 changes push default to ‘simple’
by darklajid on Saturday November 02, 2013 @03:19PM
(#6660340)
I guess I am missing something. There is no 'server'. You should have the same reflog locally, if you pulled before someone messed the repository up?
Re:Git 2.0 changes push default to ‘simple’
by luchs on Saturday November 02, 2013 @03:47PM
(#6660460)
The 'server' in this case is a remote repository which has some commits you don't have. If you force push to this repository, these commits will be lost for you - only the person who pushed these or someone with access to the server can restore them.
Re:Git 2.0 changes push default to ‘simple’
by judk on Saturday November 02, 2013 @03:02PM
(#6660275)
Today I suddenly realized reflog is "ref log" not "re flog". My world just got a bit less magical.
Re:Git 2.0 changes push default to ‘simple’
by eru on Saturday November 02, 2013 @03:32PM
(#6660399)
Has someone told you about "we blog" yet?