From: Junio C Hamano <junkio@cox•net>
To: Julian Phillips <julian@quantumfyre•co.uk>
Cc: git@vger•kernel.org, Andy Parkins <andyparkins@gmail•com>
Subject: Re: [PATCH 0/2] bookmarks
Date: Wed, 25 Apr 2007 22:53:11 -0700 [thread overview]
Message-ID: <7vmz0vu1fc.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0704252332170.18446@beast.quantumfyre.co.uk> (Julian Phillips's message of "Wed, 25 Apr 2007 23:51:27 +0100 (BST)")
Julian Phillips <julian@quantumfyre•co.uk> writes:
> While I like the idea of private tags, I find the idea of them having
> their own namespace to be much more attractive than simply having the
> ability to not export lightweight tags.
>
> In particular it means that you can control which tags are exported
> individually.
I do not think this is limited to tags. Sometimes you may want
to make some branches private. It probably is also a good idea
to hide StGIT patch base refs that live under $GIT_DIR/refs/.
Here, I do not use the word "private" in the sense of being
"secret", as most likely branches that share common root would
have many trees and blobs in common, but in the sense of "less
clutter".
How would one find out about remote refs? By running
ls-remote. And that happens to also be how git-fetch follows
tags (the original issue Andy had).
Over native git protocol, upload-pack is the program that runs
in the repote repository and gives list of available refs and
object names they point at (upload-pack.c::send_ref()). To dumb
clients, update-server-info creates the equivalent information
in $GIT_DIR/info/refs and that is what the ls-remote sees.
So I suspect that a more general solution would be to to teach
these two programs to take notice of a new configuration
variable you can set in the repository to limit the set of refs
to give out. Then you do not have to introduce a new namespace,
Probably the configuration would be a glob pattern (for pathname
like things, we tend to use shell glob, not regexp) to
include/exclude. E.g.
refs.expose = refs/heads/*
refs.expose = refs/tags/*
refs.expose = !refs/heads/*/*
refs.expose = !refs/tags/v[0-9]*
would let you say "I would want to expose all of refs/heads/
(i.e. branches) and refs/tags (i.e. tags), but I do not want to
show branches with '/' in their names, nor tags whose names do
not begin with v[0-9]".
next prev parent reply other threads:[~2007-04-26 5:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 19:04 git-fetch and unannotated tags Andy Parkins
2007-04-25 19:59 ` Julian Phillips
2007-04-25 20:42 ` Andy Parkins
2007-04-25 21:00 ` Junio C Hamano
2007-04-26 8:04 ` Andy Parkins
2007-04-26 15:21 ` Andreas Ericsson
2007-04-27 15:50 ` Jakub Narebski
2007-04-29 6:44 ` Junio C Hamano
2007-04-25 22:51 ` [PATCH 0/2] bookmarks (was: Re: git-fetch and unannotated tags) Julian Phillips
2007-04-25 22:25 ` [PATCH 1/2] refs.c: change do_one_ref to not discard any of base Julian Phillips
2007-04-25 22:29 ` [PATCH 2/2] Add basic support for bookmarks (create/edit/delete/list) Julian Phillips
2007-04-26 0:17 ` A Large Angry SCM
2007-04-26 0:29 ` Jeffrey C. Ollie
2007-04-26 5:53 ` Junio C Hamano [this message]
2007-04-26 7:25 ` [PATCH 0/2] bookmarks Julian Phillips
2007-04-26 7:50 ` Junio C Hamano
2007-04-26 9:04 ` Julian Phillips
2007-04-26 8:23 ` Andy Parkins
2007-04-26 8:33 ` Andy Parkins
2007-04-26 17:09 ` Petr Baudis
2007-04-26 8:08 ` [PATCH 0/2] bookmarks (was: Re: git-fetch and unannotated tags) Andy Parkins
2007-04-26 9:00 ` Julian Phillips
2007-04-26 13:45 ` Karl Hasselström
2007-04-26 16:19 ` Linus Torvalds
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=7vmz0vu1fc.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox$(echo .)net \
--cc=andyparkins@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=julian@quantumfyre$(echo .)co.uk \
/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