threads / discuss / 918

cogito and tags propagation

Subject: cogito and tags propagation

## tl;dr

3 messages between Jun 12, 2005 and Jun 12, 2005.

replies: 2people: 2as markdown or json

Jon Smirl· Jun 12, 2005, 15:50 UTC · lore

If I add a tag to tree A, then go to tree B which depends on A and do cg update. It says the branch is already fully merged. It's not counting the addition of a tag as something that marks the tree dirty.

-- 
Jon Smirl
jonsmirl@gmail.com
Zack Brown· Jun 12, 2005, 17:49 UTC · re: Jon Smirl · lore

Re: cogito and tags propagation

On Sun, Jun 12, 2005 at 11:50:08AM -0400, Jon Smirl wrote:
> If I add a tag to tree A,  then go to tree B which depends on A and do
> cg update. It says the branch is already fully merged. It's not
> counting the addition of a tag as something that marks the tree dirty.

My impression is that tags are local to a given repo, i.e. they are not included by default in the publically accessible data. The repo owner has to somehow 'tell' people about the tags, in order for them to be able to get them.

Apparently this is useful because it allows smaller groups to work together with their own 'local' tags, without polluting the main tree.

Be well, Zack

Show 8 quoted lines
> 
> -- 
> Jon Smirl
> jonsmirl@gmail.com
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
Zack Brown
Jon Smirl· Jun 12, 2005, 17:54 UTC · re: Zack Brown · lore

Re: cogito and tags propagation

On 6/12/05, Zack Brown <zbrown@tumblerings.org> wrote:
Show 8 quoted lines
> On Sun, Jun 12, 2005 at 11:50:08AM -0400, Jon Smirl wrote:
> > If I add a tag to tree A,  then go to tree B which depends on A and do
> > cg update. It says the branch is already fully merged. It's not
> > counting the addition of a tag as something that marks the tree dirty.
> 
> My impression is that tags are local to a given repo, i.e. they are not included
> by default in the publically accessible data. The repo owner has to somehow
> 'tell' people about the tags, in order for them to be able to get them.

I have a bunch of tags in my repo that have been cloned from linus. So the tags do move through the system. But it seems that they need a commit to make them move, apparently creating a new tag doesn't count as a commit (and make a new tree head id).

[jonsmirl@jonsmirl .git]$ ls refs/tags v2.6.11 v2.6.11-tree v2.6.12-rc2 v2.6.12-rc3 v2.6.12-rc4 v2.6.12-rc5 v2.6.12-rc6

Show 19 quoted lines
> 
> Apparently this is useful because it allows smaller groups to work together with
> their own 'local' tags, without polluting the main tree.
> 
> Be well,
> Zack
> 
> >
> > --
> > Jon Smirl
> > jonsmirl@gmail.com
> > -
> > To unsubscribe from this list: send the line "unsubscribe git" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> --
> Zack Brown
> 
-- 
Jon Smirl
jonsmirl@gmail.com

← back to recent threads