git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: PJ Weisberg <pj@irregularexpressions.net>
To: dquince <devin.quince@troppussoftware.com>
Cc: git@vger.kernel.org
Subject: Re: Cloning tags from master
Date: Mon, 15 Oct 2012 20:08:13 -0700	[thread overview]
Message-ID: <CAJsNXT=JHds1fxDVYECXhVaRgkgFg6-amGBRy6HQDgxOiUOkkg@mail.gmail.com> (raw)
In-Reply-To: <1350330293914-7569301.post@n2.nabble.com>

On Mon, Oct 15, 2012 at 12:44 PM, dquince
<devin.quince@troppussoftware.com> wrote:
> I am trying to implement using tags in our build process, but am running into
> an issue with pulling tags from master. My scenario is as follows
> We decide on a release and I tag master with testtag which has commit
> testtag-1-gf3b117e
> When I make another commit to master and check the tag, I see it as
> testtag-2-gfb56442

I don't know what you mean by "check the tag", but those look like the
output of "git describe" when HEAD is one or two commits ahead of
testtag (with no tags that are closer).

> When I try and pull the tag using testtag, it just wants to pull the latest
> commit to master.

You're probably not running "git pull origin refs/tags/testtag", but I
think that's the only way to "pull the tag," so I don't know what
you're doing here.  The tag doesn't include anything that's not part
of the tag's history, though, so "pulling" it won't get the latest
version of anything.

> I verified this works in branches other than master, so can this be done
> from master or does the tag just follow the head?

Tags never follow anything.  Once they're created, they stay put.

-PJ

Gehm's Corollary to Clark's Law: Any technology distinguishable from
magic is insufficiently advanced.

      reply	other threads:[~2012-10-16  3:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15 19:44 Cloning tags from master dquince
2012-10-16  3:08 ` PJ Weisberg [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJsNXT=JHds1fxDVYECXhVaRgkgFg6-amGBRy6HQDgxOiUOkkg@mail.gmail.com' \
    --to=pj@irregularexpressions.net \
    --cc=devin.quince@troppussoftware.com \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).