git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: any way to apply tag across all branches in repository?

From
Brandon Casey <casey@nrlssc.navy.mil>
Date
May 19, 2009, 19:58 UTC
Message-ID
<ZSs3H_GRUGTI_yYwSwXULjkMD8YR-hSkoePTFq0NfYvkbDV9N7CgMw@cipher.nrlssc.navy.mil>
In-Reply-To
<4A130D45.1050207@nortel.com>
Chris Friesen wrote:
> Brandon Casey wrote:
Show 11 quoted lines
> <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.

Based on this, and your other message, it sounds like you want to have a tag named 'v1.2.3' which is treated differently for each branch. Since there is only a single tag namespace, this is not possible. Tag names must be unique.

You can also use slashes in tag names. Perhaps you could have the illusion of common version numbers by using tag names like $arch/$version?

-brandon
Previous: Chris Friesen
Message 16 of 16 in “any way to apply tag across all branches in repository?”
  1. Chris FriesenMay 19, 2009
  2. Tomas CarneckyMay 19, 2009
  3. Chris FriesenMay 19, 2009
  4. Brandon CaseyMay 19, 2009
  5. Chris FriesenMay 19, 2009
  6. Linus TorvaldsMay 19, 2009
  7. Chris FriesenMay 19, 2009
  8. Linus TorvaldsMay 19, 2009
  9. Chris FriesenMay 19, 2009
  10. Linus TorvaldsMay 19, 2009
  11. Chris FriesenMay 19, 2009
  12. Brandon CaseyMay 19, 2009
  13. Chris FriesenMay 19, 2009
  14. Brandon CaseyMay 19, 2009
  15. Chris FriesenMay 19, 2009
  16. Brandon CaseyMay 19, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.