From: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
To: git@vger.kernel.org
Cc: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
Subject: [PATCH v2] gitk: add -C <path> commandline parameter to change path
Date: Thu, 5 Nov 2015 11:19:24 +0200 [thread overview]
Message-ID: <1446715164-19165-1-git-send-email-juhapekka.heikkila@gmail.com> (raw)
In-Reply-To: <CAPig+cSs0v88AiQwSrqm-wK7rY4RdykaVf5Axh5jFyij25rfvg@mail.gmail.com>
This patch adds -C (change working directory) parameter to
gitk. With this parameter, instead of need to cd to directory
with .git folder, one can point the correct folder from
commandline.
v2: Adjusted the parameter as per Eric's suggestion. I think
it now work in similar manner as in many GNU tools as well
as git itself.
Signed-off-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
---
Documentation/gitk.txt | 7 +++++++
gitk-git/gitk | 26 +++++++++++++++++---------
2 files changed, 24 insertions(+), 9 deletions(-)
diff --git a/Documentation/gitk.txt b/Documentation/gitk.txt
index 6ade002..d194d9b 100644
--- a/Documentation/gitk.txt
+++ b/Documentation/gitk.txt
@@ -146,6 +146,13 @@ gitk-specific options
Select the specified commit after loading the graph.
Default behavior is equivalent to specifying '--select-commit=HEAD'.
+-C <path>::
+
+ Run as if gitk was started in '<path>' instead of the current
+ working directory. When multiple `-C` options are given, each
+ subsequent non-absolute `-C <path>` is interpreted relative to
+ the preceding `-C <path>`.
+
Examples
--------
gitk v2.6.12.. include/scsi drivers/scsi::
diff --git a/gitk-git/gitk b/gitk-git/gitk
index fcc606e..606474a 100755
--- a/gitk-git/gitk
+++ b/gitk-git/gitk
@@ -12279,20 +12279,14 @@ setui $uicolor
setoptions
-# check that we can find a .git directory somewhere...
-if {[catch {set gitdir [exec git rev-parse --git-dir]}]} {
- show_error {} . [mc "Cannot find a git repository here."]
- exit 1
-}
-
set selecthead {}
set selectheadid {}
set revtreeargs {}
set cmdline_files {}
-set i 0
set revtreeargscmd {}
-foreach arg $argv {
+for {set i 0} {$i < [llength $argv]} {incr i} {
+ set arg [lindex $argv [expr {$i}]]
switch -glob -- $arg {
"" { }
"--" {
@@ -12305,11 +12299,25 @@ foreach arg $argv {
"--argscmd=*" {
set revtreeargscmd [string range $arg 10 end]
}
+ "-C*" {
+ if {[string length $arg] < 3} {
+ incr i
+ cd [lindex $argv [expr {$i}]]
+ continue
+ } else {
+ cd [string range $arg 2 end]
+ }
+ }
default {
lappend revtreeargs $arg
}
}
- incr i
+}
+
+# check that we can find a .git directory somewhere...
+if {[catch {set gitdir [exec git rev-parse --git-dir]}]} {
+ show_error {} . [mc "Cannot find a git repository here."]
+ exit 1
}
if {$selecthead eq "HEAD"} {
--
1.9.1
next prev parent reply other threads:[~2015-11-05 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 15:00 [PATCH 0/1] gitk: add --cwd=path commandline parameter to change path Juha-Pekka Heikkila
2015-11-03 15:00 ` [PATCH 1/1] " Juha-Pekka Heikkila
2015-11-03 18:27 ` Eric Sunshine
2015-11-05 9:19 ` Juha-Pekka Heikkila [this message]
2015-11-06 9:48 ` [PATCH v2] gitk: add -C <path> " Eric Sunshine
2015-11-06 10:49 ` Juha-Pekka Heikkila
2015-11-09 11:45 ` [PATCH v3] " Juha-Pekka Heikkila
2015-12-19 3:13 ` Paul Mackerras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1446715164-19165-1-git-send-email-juhapekka.heikkila@gmail.com \
--to=juhapekka.heikkila@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).