Git submodules - another puzzle - reference is not a tree?

I suppose the commit was lost when she solved the submodule conflict. It can be retrieved by following instructions in this question Or run gitk --all $( git fsck --no-reflog | awk '/dangling commit/ {print $3}' ) (This is from this question ) Only do it on the original repo (as git clone will delete dangling commits), and make a backup of it before.

I suppose the commit was lost when she solved the submodule conflict. It can be retrieved by following instructions in this question. Or run gitk --all $( git fsck --no-reflog | awk '/dangling commit/ {print $3}' ) (This is from this question) Only do it on the original repo (as git clone will delete dangling commits), and make a backup of it before.

– user561638 Jul 14 at 17:08 This may be another question, I don't know submodules very well... But being careful on merging wild beast such as submodule must be done very carefully. – CharlesB Jul 15 at 6:45 BTW did she recover the commit? – CharlesB Jul 15 at 6:45 No, she didn't wait for me to be in work.

She re-implemented the changes. – user561638 Jul 15 at 18:37.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.