From: Marc Branchaud <marcnarc@xiplink.com>
To: Stephen Bash <bash@genarts.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC] Hidden refs
Date: Wed, 13 Oct 2010 12:14:00 -0400 [thread overview]
Message-ID: <4CB5DAC8.7000004@xiplink.com> (raw)
In-Reply-To: <3305459.485811.1286983945370.JavaMail.root@mail.hq.genarts.com>
On 10-10-13 11:32 AM, Stephen Bash wrote:
>> 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).
Hmm, maybe I'm just over-designing.
It's true that we could just use refs/builds (instead of .builds) and that
those refs would need to be explicitly retrieved by anyone who wanted to see
them (which is fine). And after the builds/ refs are fetched and done with,
it's easy enough to get rid of them with a simple "rm -r .git/refs/builds"
It appears all I'm looking for is a way to avoid that rm command. Seems a
bit silly in the end.
Thanks for the perspective!
M.
next prev parent reply other threads:[~2010-10-13 16:13 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
2010-10-13 16:14 ` Marc Branchaud [this message]
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
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=4CB5DAC8.7000004@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=bash@genarts.com \
--cc=git@vger.kernel.org \
/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).