All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: Zack Brown <zbrown@tumblerings.org>
Cc: git <git@vger.kernel.org>
Subject: Re: cogito and tags propagation
Date: Sun, 12 Jun 2005 13:54:44 -0400	[thread overview]
Message-ID: <9e473391050612105461005e3f@mail.gmail.com> (raw)
In-Reply-To: <20050612174905.GA18751@tumblerings.org>

On 6/12/05, Zack Brown <zbrown@tumblerings.org> 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

      reply	other threads:[~2005-06-12 17:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-12 15:50 cogito and tags propagation Jon Smirl
2005-06-12 17:49 ` Zack Brown
2005-06-12 17:54   ` Jon Smirl [this message]

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=9e473391050612105461005e3f@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=zbrown@tumblerings.org \
    /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.