git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: git@vger.kernel.org
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
	Junio C Hamano <gitster@pobox.com>,
	Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Subject: [PATCH 0/3] git-gui: generic and robust worktree/gitdir support
Date: Mon,  9 Feb 2009 03:00:47 +0100	[thread overview]
Message-ID: <1234144850-2903-1-git-send-email-giuseppe.bilotta@gmail.com> (raw)

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

             reply	other threads:[~2009-02-09  2:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09  2:00 Giuseppe Bilotta [this message]
2009-02-09  2:00 ` [PATCH 1/3] git-gui: properly check for a bare repo Giuseppe Bilotta
2009-02-18 17:16   ` Shawn O. Pearce
2009-02-18 21:47     ` Giuseppe Bilotta
2009-02-18 21:53       ` Shawn O. Pearce
2009-02-09  2:00 ` [PATCH 2/3] git-gui: use the actual worktree Giuseppe Bilotta
2009-02-18 17:22   ` Shawn O. Pearce
2009-02-09  2:00 ` [PATCH 3/3] git-gui: define correct GIT_DIR for gitk Giuseppe Bilotta
2009-02-18 17:22   ` Shawn O. Pearce

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1234144850-2903-1-git-send-email-giuseppe.bilotta@gmail.com \
    --to=giuseppe.bilotta@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=spearce@spearce.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.
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 NNTP newsgroup(s).