From: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
Subject: [PATCH 0/8] make gitk work better in non-top-level directory
Date: Mon, 4 Apr 2011 22:14:11 -0400 [thread overview]
Message-ID: <1301969659-19703-1-git-send-email-martin.von.zweigbergk@gmail.com> (raw)
This series fixes a few different bugs in gitk related to its working
directory.
I started working on patch 1, which fixes "Highlight this only/too"
when gitk is started in a subdirectory. This problem has bothered me
for a long time, but I had heard that the Tcl code in gitk was hard to
maintain, so I didn't have a look at it until now. I have to say that
it was a lot easier to follow the code than I had feared.
While testing that the fix in patch 1 worked, I found that gitk does
not work very well when the work tree is not at ".git/..", so most of
the other patches try to improve that situation.
I think I have tested most combinations of setups (top-level dir,
subdir, separate work tree, bare repo, .git) and operations (highlight
file, blame, external diff, show origin of line).
Martin von Zweigbergk (8):
gitk: fix file highlight when run in subdirectory
gitk: fix "show origin of this line" with separate work tree
gitk: fix "blame parent commit" with separate work tree
gitk: fix "External diff" with separate work tree
gitk: put temporary directory inside .git
gitk: run 'git rev-parse --git-dir' only once
gitk: simplify calculation of gitdir
gitk: show modified files with separate work tree
gitk-git/gitk | 59 +++++++++++++++++++++++++++++++-------------------------
1 files changed, 33 insertions(+), 26 deletions(-)
--
1.7.4.79.gcbe20
next reply other threads:[~2011-04-05 2:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 2:14 Martin von Zweigbergk [this message]
2011-04-05 2:14 ` [PATCH 1/8] gitk: fix file highlight when run in subdirectory Martin von Zweigbergk
2011-04-10 1:54 ` Paul Mackerras
2011-04-10 18:03 ` Martin von Zweigbergk
2011-04-05 2:14 ` [PATCH 2/8] gitk: fix "show origin of this line" with separate work tree Martin von Zweigbergk
2011-04-05 2:14 ` [PATCH 3/8] gitk: fix "blame parent commit" " Martin von Zweigbergk
2011-04-05 2:14 ` [PATCH 4/8] gitk: fix "External diff" " Martin von Zweigbergk
2011-04-05 2:14 ` [PATCH 5/8] gitk: put temporary directory inside .git Martin von Zweigbergk
2011-04-05 2:14 ` [PATCH 6/8] gitk: run 'git rev-parse --git-dir' only once Martin von Zweigbergk
2011-04-05 2:14 ` [PATCH 7/8] gitk: simplify calculation of gitdir Martin von Zweigbergk
2011-04-05 2:14 ` [PATCH 8/8] gitk: show modified files with separate work tree Martin von Zweigbergk
2011-04-10 2:03 ` Paul Mackerras
2011-04-11 19:15 ` Junio C Hamano
2011-05-24 2:44 ` [PATCH v2 " Martin von Zweigbergk
2011-04-05 18:48 ` [PATCH 0/8] make gitk work better in non-top-level directory Peter Baumann
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=1301969659-19703-1-git-send-email-martin.von.zweigbergk@gmail.com \
--to=martin.von.zweigbergk@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=paulus@samba.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).