From: Stephen Bash <bash@genarts.com>
To: Marc Branchaud <marcnarc@xiplink.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC] Hidden refs
Date: Wed, 13 Oct 2010 11:32:25 -0400 (EDT) [thread overview]
Message-ID: <3305459.485811.1286983945370.JavaMail.root@mail.hq.genarts.com> (raw)
In-Reply-To: <4CB5CEA3.8020702@xiplink.com>
> So I'm wondering if it makes sense to properly support hidden
> directories in
> refs/, and what it would take to do so. (I image, for example, that
> things
> would behave quite differently on Windows...)
>
> Thoughts?
We currently use refs/hidden/heads and refs/hidden/tags for hidden refs. It does require calling 'gitk --branches --tags' rather than 'gitk --all', but otherwise I like the behavior (git branch only lists refs/heads, git tag only lists ref/tags). And they never get cloned by default (they can still be fetched when needed).
Stephen
next prev parent reply other threads:[~2010-10-13 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 15:22 [RFC] Hidden refs Marc Branchaud
2010-10-13 15:32 ` Stephen Bash [this message]
2010-10-13 16:14 ` Marc Branchaud
2010-10-13 17:35 ` Jeff King
2010-10-13 17:42 ` Junio C Hamano
2010-10-13 17:46 ` Jeff King
2010-10-13 17:51 ` Junio C Hamano
2010-10-13 17:53 ` Jonathan Nieder
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=3305459.485811.1286983945370.JavaMail.root@mail.hq.genarts.com \
--to=bash@genarts.com \
--cc=git@vger.kernel.org \
--cc=marcnarc@xiplink.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.