All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 08 Mar 2006 11:13:08 +0100	[thread overview]
Message-ID: <440EAE34.5020807@op5.se> (raw)
In-Reply-To: <440E5E40.7090700@gmail.com>

A Large Angry SCM wrote:
> 
> Why is a "pull" bothering with tags? A "fetch" yes, but not a pull.
> 

A pull is a fetch + merge. I said pull because what little I know of 
Linus' workflow is the the emails he gets from susbsystem maintainers 
are called "pull requests".

>>
>> 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.
> 
> 
> The distinction here is not annotated tags or temporary tags but _local_ 
> tags. _Your_ workflow conventions treat unannotated tags as local tags 
> but declaring that unannotated tags can not be pushed is imposing _your_ 
> conventions on other groups. Just as branch names, themselves, can be 
> meaningful, so can tag names.
> 

Yes, that's why I said it's better to discourage than to disallow. The 
default update-hook is disabled by default and there are comments 
aplenty to make it possible even for the most die-hard point-and-click 
monkey to be able to comment out the disallowing of unannotated tags.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

  reply	other threads:[~2006-03-08 10:13 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
2006-03-07 18:10             ` Junio C Hamano
2006-03-08  4:32             ` A Large Angry SCM
2006-03-08 10:13               ` Andreas Ericsson [this message]
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=440EAE34.5020807@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 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.