" commit holds the content of the index (the staged files)Īs you can see, these commits are based on the active commit at the moment when you run git stash. the top commit itself holds the content of your worktree (files on disk, including not yet staged changes).| * d9f6a3e index on master: ba7d0ba create a.txt * df1c341 (refs/stash) WIP on master: ba7d0ba create a.txt You can have a view of that by running git log -oneline -graph stash : $ git log -oneline -graph stash Perhaps you weren't aware of it: git stash actually stores changes in git by creating a commit (a regular merge commit). No changes added to commit (use "git add" and/or "git commit -a")ĭropped (d9c5f5a5121c5d8e183d0efa7e9533c53420a344)īut only some of them were retrieved, why? what can I do now? Modified: Sources/MCAL/Config/Opb_cfg.cfg Modified: Sources/MCAL/Config/Dio_cfg.cfg Modified: Sources/IoHwAb/InterCom/InterComSignalIf/InterComSignalIf_DiagRequests.c " to discard changes in working directory) It then I wanted to retrieve them back with git stash pop command: MINGW64 /c/Daten/Projekte/nextgen_coolant/HvUnit (feature_184932) Sources/SimpleRealTimeScheduler/Srts_Slots_Cfg.c | 4 +-ġ0 files changed, 110 insertions(+), 100 deletions(-) Sources/SimpleRealTimeScheduler/Srts_Cfg.c | 2 +. Sources/SimpleRealTimeScheduler/Srts.h | 2 +. Sources/SimpleRealTimeScheduler/Srts.c | 22 +. I stashed all changes which I could see all with git stash show command: MINGW64 /c/Daten/Projekte/nextgen_coolant/HvUnit (feature_184932)
0 Comments
Leave a Reply. |