From: Joshua Jensen <jjensen@workspacewhiz•com>
To: Sverre Rabbelier <srabbelier@gmail•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 10:07:31 -0600 [thread overview]
Message-ID: <4C6C0543.7070203@workspacewhiz.com> (raw)
In-Reply-To: <AANLkTi=4Jr6KknLyBUe_+bQ4zue2KGNjxJtY8Ja6LmAT@mail.gmail.com>
----- Original Message -----
From: Sverre Rabbelier
Date: 8/17/2010 11:42 AM
> 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
next prev parent reply other threads:[~2010-08-18 16:07 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 [this message]
2010-08-18 16:23 ` Chris Packham
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=4C6C0543.7070203@workspacewhiz.com \
--to=jjensen@workspacewhiz$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=srabbelier@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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