From this log, it looks like =85bad3f= and =14f8eed= are the relevant commits, and there are others listed that are not pertinent. (If the ticket numbers are not in the commit message, the =git log= command is useless for this.)
-Now you can do
-
+Now you can do (for some reason, =git tag --contains= takes longer than it should...)
{code}
-git branch -a --contains 85bad3f
+git tag --contains 85bad3f | grep -E '^V[[:digit:]]+_[[:digit:]]+_[[:digit:]]+$'
{endcode}
-
which produces the list
-
{code}
-<Snipped, for brevity>
-remotes/origin/V7_6-winslotuser-publicbranch
-remotes/origin/V7_6_1-branch
-remotes/origin/V7_6_2-branch
-remotes/origin/V7_7-allow_cleanup_final_dag_node-branch
-<Again snipped for brevity>
+V7_6_1
+V7_6_2
+V7_7_0
{endcode}
-
-Thus it appears the feature introduced in #2004 was first released in 7.6.1.
-
-Old branches get 'bag-and-tag'-ed: the branches are moved from =/refs/heads= to =/refs/tags=, and suffixed with "=-tag=". You can use =git tag --contains= instead of =git branch --contains= above to find the tags that contain the commit.
+Thus we know the feature (or bugfix) in #2004 was first released in 7.6.1.
