Chris Friesen wrote: > Hi all, > > I'm hoping you can help me out...please CC me on replies, I'm not > subscribed to the list. > > We have a piece of software with a "main" branch and multiple > architecture-specific "target" branches. At each "official" compile, > we'd like to tag the commits that went into that compile with an identifier. > > Using tags normally requires that the tag be assigned to each branch > individually--is there any way to apply some sort of designator to the > head of each branch in the repository all at once rather than doing it > separately for each branch? If I understand you correctly, you are doing your primary development on the "main" branch and then merging this into the architecture specific branches which contain additional architecture specific changes. All you need to do is tag the "main" branch. Actually, you are tagging the commit that the branch currently points at. When this branch is merged into the other branches, they will also contain this commit, and 'git describe' will use the tag you created when generating the version string. -brandon -- 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