git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org, Julian Phillips <julian@quantumfyre.co.uk>,
	Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH 0/2] bookmarks
Date: Thu, 26 Apr 2007 19:09:08 +0200	[thread overview]
Message-ID: <20070426170908.GS4489@pasky.or.cz> (raw)
In-Reply-To: <200704260933.38677.andyparkins@gmail.com>

On Thu, Apr 26, 2007 at 10:33:36AM CEST, Andy Parkins wrote:
> On Thursday 2007 April 26, Andy Parkins wrote:
> 
> > Actually how about this: an option in the remote section to turn off
> > auto-following and then add fetch and push lines for the tags too - that
> > means very minimal changes and then everyone's happy (where everyone =
> > me ;-)).
> 
> Funny.  I went looking to add the above facility, and lo-and-behold, it's 
> already there in the form of the remote.$remote.tagopt parameter.
> 
> [remote "origin"]
>    tagopt = --no-tags
>    push = refs/tags/public:refs/tags/*
>    fetch = refs/tags/*:refs/tags/public/*
> 
> This does exactly what I want.  Once again, git is waaaay ahead of me :-)

Still, I think it would be nice to have an "out-of-the-box" general
solution for this. And since as Junio said, it might be nice to have
private heads as well, I might mention my ancient proposal to just keep
refs with filename starting with a dot (refs/tags/.foo, ...) private by
default. I have discussed this with Junio and IIRC he wasn't very happy
with this proposal, but I can't remember his arguments now. :-(

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Ever try. Ever fail. No matter. // Try again. Fail again. Fail better.
		-- Samuel Beckett

  reply	other threads:[~2007-04-26 17:11 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       ` [PATCH 0/2] bookmarks Junio C Hamano
2007-04-26  7:25         ` 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 [this message]
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=20070426170908.GS4489@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=julian@quantumfyre.co.uk \
    --cc=junkio@cox.net \
    /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 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 NNTP newsgroup(s).