Shorter version: if you have a cloned git repo, git tag -d openafs-devel-1_7_18
When we do a release the tag is supposed to be applied to the relevant point on the branch the release is done from; The master branch, not being used for releases, is not being tagged. Unfortunately, the 1.7.18 tag was applied to the master, not the 1.7 branch. This would mean that the tools which attempt to describe a checkout would describe future builds from master as descendents of 1.7.18, which is not desirable. To that end we removed the tag upstream, and would request that you do the same. A 1.7.18a tag describing the same code will be pushed momentarily; A new set of binaries will not be done. -- Derrick _______________________________________________ OpenAFS-devel mailing list OpenAFS-devel@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-devel
