From: Joshua Jensen <jjensen@workspacewhiz.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Storing notes refs outside of refs/
Date: Thu, 26 Aug 2010 13:20:48 -0600 [thread overview]
Message-ID: <4C76BE90.6040902@workspacewhiz.com> (raw)
In-Reply-To: <7vlj7tkxvn.fsf@alter.siamese.dyndns.org>
----- Original Message -----
From: Junio C Hamano
Date: 8/26/2010 12:54 PM
> Joshua Jensen<jjensen@workspacewhiz.com> writes
>> gitk --all --not --glob=refs/notes/*
>>
>> does not work.
> I don't think --not there is a good idea because "--not" in rev-list
> parameter means "not reachable from the following commits".
Okay. I've not used it before.
> It may be useful if you made "--all --glob=!refs/notes/*" to work,
> though. I could picture myself buying such a change.
>
> Or just use "--branches --tags" instead, perhaps?
gitk --branches --remotes --tags is long to type. (Let's ignore git
aliases for the moment.)
The deal is, refs/notes/ showing in git log --all serves no purpose, in
my opinion. If it does for somebody else, I'd love to hear.
What if there was a configuration setting applied to 'git log --all' as
a filter for refs I never want to see in the --all view?
git config --add core.logfilter refs/notes/*
git config --add core.logfilter refs/game-p4/*
I also like the negated --glob syntax you showed above.
Another possibly useful idea is an extra 'git log' parameter --brt (for
--branches, --remotes, --tags).
Thoughts? I'll see if I can find some time to work on something once I
have a bit of direction.
Josh
next prev parent reply other threads:[~2010-08-26 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 15:02 Storing notes refs outside of refs/ Joshua Jensen
2010-08-26 17:05 ` Junio C Hamano
2010-08-26 18:25 ` Joshua Jensen
2010-08-26 18:54 ` Junio C Hamano
2010-08-26 19:20 ` Joshua Jensen [this message]
2010-08-26 18:47 ` Tomas Carnecky
2010-08-26 18:51 ` Sverre Rabbelier
2010-08-26 19:09 ` Tomas Carnecky
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=4C76BE90.6040902@workspacewhiz.com \
--to=jjensen@workspacewhiz.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.