git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 0/3] git-gui: generic and robust worktree/gitdir support

From
Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date
Feb 9, 2009, 02:00 UTC
Message-ID
<1234144850-2903-1-git-send-email-giuseppe.bilotta@gmail.com>
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
Next: Giuseppe Bilotta
Message 1 of 9 in “git-gui: generic and robust worktree/gitdir support”
  1. 0/3 git-gui: generic and robust worktree/gitdir supportGiuseppe Bilotta, Feb 9, 2009
  2. 1/3 git-gui: properly check for a bare repoGiuseppe Bilotta, Feb 9, 2009
  3. Shawn O. PearceFeb 18, 2009
  4. Giuseppe BilottaFeb 18, 2009
  5. Shawn O. PearceFeb 18, 2009
  6. 2/3 git-gui: use the actual worktreeGiuseppe Bilotta, Feb 9, 2009
  7. Shawn O. PearceFeb 18, 2009
  8. 3/3 git-gui: define correct GIT_DIR for gitkGiuseppe Bilotta, Feb 9, 2009
  9. Shawn O. PearceFeb 18, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.