From: Yann Dirson <ydirson@altern.org>
Date: Tue, 09 Jan 2007 19:41:08 GMT
Subject: Re: Getting gitk to display all refs but stgit logs
Message-ID: <20070109194108.GC17093@nan92-1-81-57-214-146.fbx.proxad.net>
In-Reply-To: <e5bfff550701090417g3f8ab697n709721939ab36f5d@mail.gmail.com>

On Tue, Jan 09, 2007 at 01:17:57PM +0100, Marco Costalba wrote:
> On 1/8/07, Yann Dirson <ydirson@altern.org> wrote:
> >Since v0.11, StGIT creates references to keep a hand on patch logs.
> >This has the unfortunate side-effect that "gitk --all" suddenly shows
> >all those very annoying, and soon becomes unusable on
> >repositories for which was very convenient.
> >
> 
> Normally you only need branch names
> 
> gitk/qgit --all  --> practically equivalent to --> gitk/qgit <list of
> branch names>

Not exactly.  While qgit has knowledge of StGIT stacks and displays
unapplied patches [1], gitk does not, and requesting a branch only
shows the applied patches.  I have no opinion whether gitk should be
taught about them, but I'd like it to be usable on them anyway.

One thing that qgit also does not show, but which I regularly use when
viewing StGIT stacks in gitk, is the ancestry of unapplied patches
(eg. you can see at first glance whether an unapplied patch is
uptodate, or has not been ported yet atop the currently-applied ones.

[1] BTW, as of 1.5.3 it displays them backwards, causing all sors of
problems - I've not yet collected all of my comments for you, but at
least that one is sent now ;)

Best regards,
-- 
Yann.