All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Brandon Casey <casey@nrlssc.navy.mil>
Cc: git@vger.kernel.org
Subject: Re: any way to apply tag across all branches in repository?
Date: Tue, 19 May 2009 13:49:25 -0600	[thread overview]
Message-ID: <4A130D45.1050207@nortel.com> (raw)
In-Reply-To: <0WGSJO_TdUxCKWhDCupb3MaPOyPeVNH7Rs_7iKVnQcahmxUpwu8qzw@cipher.nrlssc.navy.mil>

Brandon Casey wrote:
> Chris Friesen wrote:

>> [cfriesen@localhost linux]$ git tag -m 'a test tag' my_tag ncgl
> 
> What's "ncgl"?  Another branch at the same tip as "arch"?

Oops, missed a replace.  "ncgl" is my main branch.

> Ok, you tagged main, and previously arch was at the same state,
> so 'git describe' printed out 'my_tag' for both of them.  Now,
> the arch branch is ahead of main by one commit, so you get an
> expanded string from 'git describe' (the meaning of which I
> described earlier, above).
> 
>> Now we add another tag to the main branch:
>>
>> [cfriesen@localhost linux]$ git tag -m 'a test tag' my_tag2 main
>> [cfriesen@localhost linux]$ git describe main
>> my_tag
>> [cfriesen@localhost linux]$ git describe arch
>> my_tag-1-g4c8dfa7
>>
>> I assume that since there were no code changes on the main branch,
>> it doesn't think that there is any difference between the two tags.
> 
> Right.  There is no difference.  You created another tag pointing at
> the same revision as the first tag.  Here's something else to try:

<snip>

> Starting to make sense?

Yep.  I still need whatever identifier I use to be associated with the
head of each branch.

Based on the discussion (thanks for the explanations, by the way) I
don't see any option other than looping through each branch and using
tags with the branch name embedded in them to ensure uniqueness across
the repository.

Chris

  reply	other threads:[~2009-05-19 19:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 16:26 any way to apply tag across all branches in repository? Chris Friesen
2009-05-19 16:52 ` Tomas Carnecky
2009-05-19 16:59   ` Chris Friesen
2009-05-19 17:05 ` Brandon Casey
2009-05-19 17:48   ` Chris Friesen
2009-05-19 18:33     ` Linus Torvalds
2009-05-19 19:05       ` Chris Friesen
2009-05-19 20:14         ` Linus Torvalds
2009-05-19 20:56           ` Chris Friesen
2009-05-19 21:06             ` Linus Torvalds
2009-05-19 21:31               ` Chris Friesen
2009-05-19 18:36     ` Brandon Casey
2009-05-19 19:05       ` Chris Friesen
2009-05-19 19:30         ` Brandon Casey
2009-05-19 19:49           ` Chris Friesen [this message]
2009-05-19 19:58             ` Brandon Casey
  -- strict thread matches above, loose matches on Subject: below --
2009-05-20  8:58 Mark Struberg

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=4A130D45.1050207@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=casey@nrlssc.navy.mil \
    --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.
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.