Fix stg-whatchanged to deal with conflicts already solved.
authorYann Dirson <yann.dirson@sagem.com>
Tue, 24 Jul 2007 18:57:30 +0000 (20:57 +0200)
committerCatalin Marinas <catalin.marinas@gmail.com>
Tue, 24 Jul 2007 22:47:08 +0000 (23:47 +0100)
The most reliable way I found to decide if we were in the process of
solving a conflict, including when all conflicted files have already
been marked resolved, is to check the latest patchlog entry.

Signed-off-by: Yann Dirson <ydirson@altern.org>
contrib/stg-whatchanged

index a416e97..231f4f5 100755 (executable)
@@ -24,12 +24,10 @@ fi
 # Merges via "push" leave top=bottom so we must look at old patch
 # in this case (unlike, eg., "pick --fold")
 patchdir="$(git-rev-parse --git-dir)/patches/$(stg branch)/patches/$(stg top)"
-if [ -s "$(git-rev-parse --git-dir)/conflicts" ];
-then
-    current_cmd="stg show //top.old"
-else
-    current_cmd="stg show"
-fi
+case $(stg log | head -n1) in
+    *push\(c\)*) current_cmd="stg show //top.old" ;;
+    *) current_cmd="stg show" ;;
+esac
 
 colordiff "$@" \
     -I '^index [0-9a-b]*..[0-9a-b]*' \