[anjuta-devel] 3.7.4 tag warning



Hi all,
I want to warn everyone that there are some abnormalities with the 3.7.4
tag. The tag points to a slightly different commit than the one in
master, even though the content is the same. The problem was that there
was a last minute commit made while I was making the release. When I
went to push it, git rejected the push to master but took the tag.
Pulling again allowed me to push the release update to master, but with
a different commit hash because the parent changed. So, the tag points
to a different commit, which is why you'll notice that the release in
master doesn't have the tag on it.

The release tag should be fine, other than it not fully matching up with
master.

Honestly I've never had this happen before. How should something like
this be handled?

Thanks,
James



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]