Pass arguments through git-rev-parse.

This allows the user to specify ranges more flexibly; for instance
the user can now do "gitk v2.6.12.." and see all the changes since
2.6.12.

diff --git a/gitk b/gitk
index d50999895572df511207e021e244402bc62eebba..fef705ce97af4b9b42c6016e5c13af6bb4a0e726 100755 (executable)
--- a/gitk
+++ b/gitk
@@ -14,14 +14,22 @@ proc getcommits {rargs} {
     global startmsecs nextupdate
     global ctext maincursor textcursor nlines
 
     global startmsecs nextupdate
     global ctext maincursor textcursor nlines
 

-    if {$rargs == {}} {
-       set rargs HEAD
-    }

     set commits {}
     set phase getcommits
     set startmsecs [clock clicks -milliseconds]
     set nextupdate [expr $startmsecs + 100]
     set commits {}
     set phase getcommits
     set startmsecs [clock clicks -milliseconds]
     set nextupdate [expr $startmsecs + 100]

-    if [catch {set commfd [open "|git-rev-list --merge-order $rargs" r]} err] {
+    if [catch {
+       set parse_args [concat --default HEAD --merge-order $rargs]
+       set parsed_args [split [eval exec git-rev-parse $parse_args] "\n"]
+    }] {
+       if {$rargs == {}} {
+           set rargs HEAD
+       }
+       set parsed_args [concat --merge-order $rargs]
+    }
+    if [catch {
+       set commfd [open "|git-rev-list $parsed_args" r]
+    } err] {

        puts stderr "Error executing git-rev-list: $err"
        exit 1
     }
        puts stderr "Error executing git-rev-list: $err"
        exit 1
     }