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
CFChris Friesen <cfriesen@nortel.com>
Date
May 19, 2009, 19:05 UTC
Message-ID
<4A13030D.8000000@nortel.com>
In-Reply-To
<alpine.LFD.2.01.0905191132490.3301@localhost.localdomain>
Linus Torvalds wrote:
Show 9 quoted lines
> 
> On Tue, 19 May 2009, Chris Friesen wrote:
>> However, if I make a change on the arch-specific branch, then tag the
>> main branch and merge it into the arch-specific branch, git tells me
>> the arch-specific branch is already up-to-date and the tag doesn't
>> get propagated.
> 
> You can always just do "git fetch --tags" to fetch any new tags without 
> doing anything else.

This is all in the same local repository, but with target-specific branches containing arch-specific changes on top of a common codebase. The arch-specific stuff often comes from board vendors and such, and they're never going to be merged back into the common codebase.

I'm looking for some way to conceptually tag the current head of each branch to indicate "this commit was used to build product version FOO" so that later on when we find a bug in our code we can tell which product version(s) contain the bug and need to be patched in the field.

The brute-force way to do this would be to manually loop through each branch and create a tag of the form "$branch_$version" to ensure unique tags. But I was hoping there was a more elegant way.

Chris
Previous: Linus TorvaldsNext: Linus Torvalds
Message 7 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.