Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove legacy 0.0.1 policy for Pods without commit #2335

Closed
fabiopelosin opened this issue Jul 26, 2014 · 4 comments · Fixed by CocoaPods/Core#171
Closed

Remove legacy 0.0.1 policy for Pods without commit #2335

fabiopelosin opened this issue Jul 26, 2014 · 4 comments · Fixed by CocoaPods/Core#171
Labels
d1:easy An easy ticket that is a good start for first-time contributors s3:detailed Issues with in-depth explanations and examples that make it easier to troubleshoot t1:enhancement Enhancements that have not been picked up yet. Please comment if you plan to work on it

Comments

@fabiopelosin
Copy link
Member

With trunk and the current adoption of CocoaPods it doesn't make anymore sense. This is akin to remove this line and mentions about it in the documentation.

Inspired by #2334

@segiddins
Copy link
Member

👍

@fabiopelosin
Copy link
Member Author

@CocoaPods/core ping

@orta
Copy link
Member

orta commented Sep 15, 2014

agree

@neonichu
Copy link
Member

👍

@fabiopelosin fabiopelosin added s3:detailed Issues with in-depth explanations and examples that make it easier to troubleshoot t1:enhancement Enhancements that have not been picked up yet. Please comment if you plan to work on it and removed t3:discussion These are issues that can be non-issues, and encompass best practices, or plans for the future. labels Sep 15, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
d1:easy An easy ticket that is a good start for first-time contributors s3:detailed Issues with in-depth explanations and examples that make it easier to troubleshoot t1:enhancement Enhancements that have not been picked up yet. Please comment if you plan to work on it
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants