threads / discuss / 24764

gitk: Removing Stacked Git branches from the --all view

Subject: gitk: Removing Stacked Git branches from the --all view

## tl;dr

4 messages between Aug 17, 2010 and Aug 18, 2010.

replies: 3people: 3as markdown or json

Joshua Jensen· Aug 17, 2010, 06:02 UTC · lore

  I often run 'gitk --all'.  It works great until I introduce Stacked 
Git into the equation.  StGit uses branches called branchname.stgit for 
various metadata.  The metadata turns into an ugly mess with gitk --all.

I've been playing around with various 'git log' options, but I'm not finding one that gives me the gitk --all view as if StGit were never attached to the repository. (Speaking of StGit and apps that store metadata in branches... it would be awesome to have a filter that knocks those branches out of ALL views of the data.)

Would someone mind helping me out?

Thanks.

Josh

Sverre Rabbelier· Aug 17, 2010, 17:42 UTC · re: Joshua Jensen · lore

Re: gitk: Removing Stacked Git branches from the --all view

Heya,

On Tue, Aug 17, 2010 at 01:02, Joshua Jensen <jjensen@workspacewhiz.com> wrote:

Show 5 quoted lines

> I've been playing around with various 'git log' options, but I'm not finding
> one that gives me the gitk --all view as if StGit were never attached to the
> repository.  (Speaking of StGit and apps that store metadata in branches...
> it would be awesome to have a filter that knocks those branches out of ALL
> views of the data.)

It would be easier if StGit DTRT and stored its metadata in a stgit/ namespace. That way you could just do `gitk --branches=refs/heads/`. There's (afaik) no way to specify what refs not to show, you'd need to teach 'git rev-list' a way to ignore a ref space. You'd have to teach it how to interpret something like `git rev-list --all --not --branches=refs/heads/*.stgit`.

-- 
Cheers,

Sverre Rabbelier

Joshua Jensen· Aug 18, 2010, 16:07 UTC · re: Sverre Rabbelier · lore

Re: gitk: Removing Stacked Git branches from the --all view

  ----- Original Message -----
From: Sverre Rabbelier
Date: 8/17/2010 11:42 AM

Show 12 quoted lines

> On Tue, Aug 17, 2010 at 01:02, Joshua Jensen<jjensen@workspacewhiz.com>  wrote:
>> I've been playing around with various 'git log' options, but I'm not finding
>> one that gives me the gitk --all view as if StGit were never attached to the
>> repository.  (Speaking of StGit and apps that store metadata in branches...
>> it would be awesome to have a filter that knocks those branches out of ALL
>> views of the data.)
> It would be easier if StGit DTRT and stored its metadata in a stgit/
> namespace. That way you could just do `gitk --branches=refs/heads/`.
> There's (afaik) no way to specify what refs not to show, you'd need to
> teach 'git rev-list' a way to ignore a ref space. You'd have to teach
> it how to interpret something like `git rev-list --all --not
> --branches=refs/heads/*.stgit`.

Sure, I agree StGit should the metadata in an stgit/ namespace.

In any case, it sounds like there is no way to pull this off right now.  :(

Thanks for the help!

Josh

Chris Packham· Aug 18, 2010, 16:23 UTC · re: Joshua Jensen · lore

Re: gitk: Removing Stacked Git branches from the --all view

On 16/08/10 23:02, Joshua Jensen wrote:

Show 15 quoted lines

>  I often run 'gitk --all'.  It works great until I introduce Stacked Git
> into the equation.  StGit uses branches called branchname.stgit for
> various metadata.  The metadata turns into an ugly mess with gitk --all.
> 
> I've been playing around with various 'git log' options, but I'm not
> finding one that gives me the gitk --all view as if StGit were never
> attached to the repository.  (Speaking of StGit and apps that store
> metadata in branches... it would be awesome to have a filter that knocks
> those branches out of ALL views of the data.)
> 
> Would someone mind helping me out?
> 
> Thanks.
> 
> Josh

One thing I found was 'stg log --clear' (I'm running a newish version direct from the stgit repo but I think it should be there in stgit 0.15). It gets rid of a lot (but not all) of the extra objects that pollute the 'gitk --all' output.

One word of caution is that the Stack Git log has saved me from losing work when I've done something bone headed so I tend to clear the log only when I'm sure I've got everything I need committed upstream.