From 5e8930a1798364ecc6c47997af6e9bc83b0325de Mon Sep 17 00:00:00 2001 From: Dirk Hohndel Date: Tue, 29 Mar 2016 20:46:12 -0500 Subject: If the cache was valid, we don't want to reload just because of changes This was exactly backwards. If there already are changes we do NOT want to reload - that would overwrite those changes for no good reason; after all, the starting point was correct, so why throw the changes away? Signed-off-by: Dirk Hohndel --- subsurface-core/file.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/subsurface-core/file.c b/subsurface-core/file.c index cf7b680e7..1337da3a2 100644 --- a/subsurface-core/file.c +++ b/subsurface-core/file.c @@ -453,8 +453,7 @@ int check_git_sha(const char *filename) if (git && git != dummy_git_repository) { const char *sha = get_sha(git, branch); if (!same_string(sha, "") && - same_string(sha, saved_git_id) && - !unsaved_changes()) { + same_string(sha, saved_git_id)) { fprintf(stderr, "already have loaded SHA %s - don't load again\n", sha); return 0; } -- cgit v1.2.3-70-g09d2