moved git working copy, changes no longer detected -


so had uncommitted changes in working copy. ran out of disk space moved working copy volume. git not recognize there changes committed. not sure how should solve this. thanks.

ok, let's have small summary of comes mind after little information have:

if corrupted clone copying part of (why ever), corrupted, there no magic voodoo button can solve such data loss. doubt issue here, description not fit, in such case 1 expect git complain or @ least point out missing or changed files. if remarks right, git instead not show local modifications, claims there none.

second, if somehow git lost control on files indeed have local modifications (whatever means...), there 1 thing try recover @ least part of changes: make second clone of repository other location date (remember: in git there not "server" acting central repository, there clones @ eye level). copy on files supposedly broken clone fresh one, _only files under git control, source files, images , like. in case there differences new git clone should show local modifications. can achieve same insight using diff tool compare both clones files. again: doubt issue.

instead have impression did not lose anything, unaware of situation. 2 possible aspects come mind:

  1. maybe accidentally switched branch right before, during or after move? in case being shown state of branch, not 1 before. if switch former branch see modifications again.

  2. and guess happened here: fine, had local modifications , committed them, did not push them other repository. in case git indeed not show local modifications, there none. but clone has different log (history) in case: shows commits exist locally, not in other clones (repositories). in case have push commits!

if read between lines i'd have been using centralized revision control system subversion or cvs before, since using terminology ("working copy"). git differs those, has different concepts indeed confusing @ first when switching over. confused myself ;-) gits approach make lot of sense. offers whole lot more of possibilities, features, flexibility , robustness. investing switch worth in eyes.

so, is situation? check branches, commit log , compare other clones (repositories). hope 1 of last 2 aspects described. cause in case made right, nothing lost , sun smiles @ today :-)


Comments

Popular posts from this blog

node.js - Mongoose: Cast to ObjectId failed for value on newly created object after setting the value -

gradle error "Cannot convert the provided notation to a File or URI" -

python - NameError: name 'subprocess' is not defined -