From: Chris Packham <judge.packham@gmail.com>
To: Joshua Jensen <jjensen@workspacewhiz.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: gitk: Removing Stacked Git branches from the --all view
Date: Wed, 18 Aug 2010 09:23:29 -0700 [thread overview]
Message-ID: <4C6C0901.4090702@gmail.com> (raw)
In-Reply-To: <4C6A25E5.5050707@workspacewhiz.com>
On 16/08/10 23:02, Joshua Jensen wrote:
> 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.
prev parent reply other threads:[~2010-08-18 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 6:02 gitk: Removing Stacked Git branches from the --all view Joshua Jensen
2010-08-17 17:42 ` Sverre Rabbelier
2010-08-18 16:07 ` Joshua Jensen
2010-08-18 16:23 ` Chris Packham [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C6C0901.4090702@gmail.com \
--to=judge.packham@gmail.com \
--cc=git@vger.kernel.org \
--cc=jjensen@workspacewhiz.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).