From: Andreas Ericsson <ae@op5.se>
To: gitzilla@gmail.com
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: Pulling tags from git.git
Date: Tue, 07 Mar 2006 16:35:09 +0100 [thread overview]
Message-ID: <440DA82D.3060909@op5.se> (raw)
In-Reply-To: <440D9AB0.4070305@gmail.com>
A Large Angry SCM wrote:
> Andreas Ericsson wrote:
>
>> Junio C Hamano wrote:
>>
>>> Andreas Ericsson <ae@op5.se> writes:
>>>
>>>
>>>> With the git or git+ssh protocol, tags will be autofollowed
>>>> when you do a pull (only signed tags, I think). The
>>>> auto-following is done by detecting tags that are fetched,
>>>
>>>
>>>
>>> Ah, you are correct. We do not follow lightweight tags; I am
>>> not sure if we should.
>>>
>>
>> I'm fairly sure we shouldn't. The default update-hook prevents them
>> (if enabled), and I can't for the life of me think of why anyone would
>> want to distribute such tags.
>>
>> OTOH, preventing unannotated tags from being pushed seems like a
>> better way than to not have the ability to auto-follow those same
>> tags. After all, it's better to discourage than to disallow.
>>
>
> Before you do this, please explain why unannotated tags are not useful,
> and so should not be allowed to be pushed.
Imagine Linus, getting his "please pull" emails and doing so only to
find dozens of temporary tags fetched by the pull. Junio's patch (if I
read it correctly) unconditionally fetches *ALL* tags reachable from the
top of the commit-chain, which means there is no longer any way to keep
temporary tags in a repo from which someone else will pull.
I for one riddle my repos with temporary tags whenever I'm trying
something I'm not so sure of, or find an interesting bug or a design
decision I'm not 100% sure of. Perhaps I should rather do this with
branches, but imo branches are for doing work, whereas tags just mark a
spot in the development so I easily can find them with gitk or some such.
I may be biased by the way we do things at work. In our workflow, all
tags meant to be distributed have a short note in them which explains
the rationale of the tag. For example, new versions have a very brief
changelog that sales-people get on email (a blessing, that, since we
devs no longer have to update feature-lists and such).
Tags not meant to be distributed are unannotated, and unannotated tags
are kept out of published repos which are always stored at a central
server. Everybody synchronize to those central repos, so nobody pulls
from each other. Perhaps this is how the kernel devs work too, but if it
ever changes the update hook will no longer be able to safeguard from it
and the, in my eyes, temporary tags will be distributed in a
criss-crossing mesh so no-one will ever know where it came from or who
created it or why. I.e. a Bad Thing.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2006-03-07 15:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 18:44 Pulling tags from git.git David Ho
2006-03-06 18:54 ` David Ho
2006-03-07 9:29 ` Andreas Ericsson
2006-03-07 10:33 ` Junio C Hamano
2006-03-07 12:20 ` Andreas Ericsson
2006-03-07 14:37 ` A Large Angry SCM
2006-03-07 15:35 ` Andreas Ericsson [this message]
2006-03-07 18:10 ` Junio C Hamano
2006-03-08 4:32 ` A Large Angry SCM
2006-03-08 10:13 ` Andreas Ericsson
2006-03-09 7:37 ` Florian Weimer
2006-03-09 17:24 ` Andreas Ericsson
2006-03-20 18:30 ` Florian Weimer
2006-03-20 20:31 ` Junio C Hamano
2006-03-07 16:12 ` David Ho
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=440DA82D.3060909@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=gitzilla@gmail.com \
--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).