{"issue":{"state":"open","pull_request":{"diff_url":"https://github.com/alloy/cocoapods-specs/pull/8.diff","html_url":"https://github.com/alloy/cocoapods-specs/pull/8","patch_url":"https://github.com/alloy/cocoapods-specs/pull/8.patch"},"user":{"avatar_url":"https://secure.gravatar.com/avatar/e44a5ff43a99bb69c71aeacf2e9c32ad?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"e44a5ff43a99bb69c71aeacf2e9c32ad","url":"https://api.github.com/users/mmobarak","login":"mmobarak","id":649787},"milestone":null,"labels":[],"updated_at":"2011-11-06T12:44:58Z","assignee":null,"comments":8,"closed_at":null,"url":"https://api.github.com/repos/alloy/cocoapods-specs/issues/8","body":"","html_url":"https://github.com/alloy/cocoapods-specs/issues/8","title":"Hi, Here are a few more podspecs. Thanks for starting this project!","number":8,"id":2146294,"created_at":"2011-11-04T17:29:30Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/424a9ce662b059c35063b405e160461d?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"424a9ce662b059c35063b405e160461d","url":"https://api.github.com/users/alloy","login":"alloy","id":2320},"updated_at":"2011-11-06T12:44:58Z","url":"https://api.github.com/repos/alloy/cocoapods-specs/issues/comments/2645197","body":"> With respect to versioning tags, I share your opinion Eloy. We can certainly always ask library authors to adopt such a convention, but in the interim I think it makes sense to proceed with a synthetic version number that references a specific commit. That's why I picked a very low synthetic number, 0.0.1, where the author isn't presently tagging their repo.\r\n\r\nYeah definitely, you did the right thing. I listed them only as a TODO item to remind us to contact the authors :)\r\n\r\n> As for ASIHTTPRequest, I really just needed to be able to reference a commit that contained a fix for:\r\n> \r\n> http://www.andrewtheis.net/blog/quick-fix-for-llvm-compiler-reachability-h-warnings.php\r\n> \r\n> In the absence of a tagged commit that addressed the issue, I just went with a recent commit that worked.\r\n\r\nSo what do you think about creating a repo that only contains Reachability with the fix applied?","id":2645197,"created_at":"2011-11-06T12:44:58Z"}}