# cogito and tags propagation 3 messages from 2005-06-12 to 2005-06-12. Participants: Jon Smirl, Zack Brown. Thread: https://gitlist.dev/t/918 ## Jon Smirl, 2005-06-12 15:50 Subject: cogito and tags propagation Message-ID: <9e4733910506120850f762078@mail.gmail.com> URL: https://gitlist.dev/e/9e4733910506120850f762078%40mail.gmail.com ``` 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, 2005-06-12 17:49 Subject: Re: cogito and tags propagation Message-ID: <20050612174905.GA18751@tumblerings.org> URL: https://gitlist.dev/e/20050612174905.GA18751%40tumblerings.org In-Reply-To: <9e4733910506120850f762078@mail.gmail.com> ``` 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 > > -- > 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, 2005-06-12 17:54 Subject: Re: cogito and tags propagation Message-ID: <9e473391050612105461005e3f@mail.gmail.com> URL: https://gitlist.dev/e/9e473391050612105461005e3f%40mail.gmail.com In-Reply-To: <20050612174905.GA18751@tumblerings.org> ``` On 6/12/05, Zack Brown wrote: > 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 > > 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 ```