A-hem. <intro class="shameless plug"> I've recently restarted using (and thus working on) my Zit project, the Git-based single-file content tracker ( http://git.oblomov.eu/zit ), adding support for importing RCS history (via my rcs-fast-export project, http://git.oblomov.eu/rcs-fast-export ), and even managed to run a successful rebase (which turned out to be somewhat clumsier due to the inevitably longer command lines, but perfectly feasible). My next step was looking for ways to support the graphical utilities, in particular git-gui and gitk </intro> It turns out that while gitk works pretty fine out of the box, git-gui makes a lot of guesses and assumptions about the nature and relation between the git dir and its worktree. The following three patches try to remedy the problems I came across with some simple testing. Giuseppe Bilotta (3): git-gui: properly check for a bare repo git-gui: use the actual worktree git-gui: define correct GIT_DIR for gitk -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
