summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTanu Kaskinen <tanuk@iki.fi>2022-01-12 17:17:13 +0200
committerTanu Kaskinen <tanuk@iki.fi>2022-01-12 17:54:53 +0200
commit29d196d21674a67792d66bd3a3bdf472c22a7f44 (patch)
tree2028b2ac3ec1a7333ad42553882b5ddd6135a0d1
parent59ccdf5b5509a4037d00a12b032fb99a52e6d431 (diff)
parentd70f061e1703c53aa327d3e836222e47dde86204 (diff)
Merge tag 'v1.2'
When I prepared the 1.2 release, things probably happpened in the following order: 1. I created the preparation commits. 2. I created an MR containing those commits. 3. I merged the MR using Marge. Marge amended the commit messages with links to the MR. 4. I tagged the last local commit. 5. I pushed the tag. In step 4 I should have reset my local checkout to the version on the origin repo, which had diverged from my local version due to Marge's commit message modifications. I didn't do that, so the master branch ended up pointing to a different version than the tagged commit. This merge commit makes the tagged commit part of the master branch.
0 files changed, 0 insertions, 0 deletions