Missing Commits.

[stefanpenner]

It appears that 6c2d40beb9a7952baccb5e0ede1a20ad31e08080 was once in the mainline, but it is no longer. Whats the motivation for rewriting history?

[jasperblues]

Do you have any idea what the missing commit was?

It was probably either:

• A few times I've tested a bug-fix or new feature in a hurry, then pushed a remote tag for CoocaPods. Then pulled it back again to add a few more fixes. . . (I'm not sure if pulling a remote tag removes a commit though?)
• Someone did something that they thought was embarrassing and took it out, instead of just pushing a new commit. (please don't do this!).

I'm quite sure there's no malicious reason. (Typhoon is not like openSSL. Either it works or it crashes).

[jasperblues]

@stefanpenner

If you don't have any more comments we'll close this issue. Thanks for your concern.

• Each build that we tag / push to CocoaPods undergoes stringent quality checks. We maintain high test coverage.
• We release fixes and enhancements regularly.

At the same time Typhoon is made by volunteers who contribute their own time (and sometimes $$) to bring something like this to the community. Its released "as-is" and without warranty (Apache2.0).

[jasperblues]

Ah, I know what this is now.

When pushing minor fixes or enhancements during the course of using Typhoon on a project, I got trigger happy tagging a micro-version. Rather than bumping the micro version again, the remote tag was removed and associated with another commit a very short time later.