git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: James <jtp@nc.rr.com>
Cc: git@vger.kernel.org
Subject: Re: tags disappear
Date: Sun, 28 Oct 2007 01:05:46 -0400	[thread overview]
Message-ID: <20071028050546.GR14735@spearce.org> (raw)
In-Reply-To: <C7372F7E-F29E-4E40-AE96-7AC8CB0EE0CE@nc.rr.com>

James <jtp@nc.rr.com> wrote:
> Sorry for the dumb question.  Hoping someone can lead me in the right  
> direction.
> 
> I use git in a pretty basic setup.  One branch, I'm the only user,  
> etc.  When I set up a tag (with a command like "git tag v1.1.6"), and  
> then push the changes to the server, the tag doesn't remain when I  
> clone the tree somewhere else.
> 
> Can anyone explain why, and possibly how to keep tags on a push/clone?

You need to push the tag to the server with:
  git push server tag v1.1.6

But you should make such takes annotated with "git tag -a" so they
are proper objects in their own right, rather than just refs pointing
at commits.

-- 
Shawn.

      reply	other threads:[~2007-10-28  5:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-28  4:01 tags disappear James
2007-10-28  5:05 ` Shawn O. Pearce [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=20071028050546.GR14735@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=jtp@nc.rr.com \
    /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).