Linus Torvalds wrote: > > 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html