Added ParseKit podspec

[digal]

Homepage: http://parsekit.com/
GH: https://github.com/itod/parsekit

Note: pod spec lint fails due to https://github.com/cocoapods/specs/issues/110, but passes if the condition is commented out. I've also smoke-tested it with my iOS project, and it seem to work.

[SevInf]

Specs without version tags should be added as 0.0.1

[digal]

changed version to 0.0.1

[SevInf]

Good. What about asking the author to add tags?

[digal]

Wow, you even have a template for this! Thanks.

The template assumes that podspec should be in the Specs repo. Should I wait for merge before filing the issue?

[digal]

Ok, I think I'll give a link to this pull request.

[digal]

Here it is: itod/parsekit#12

[SevInf]

Thank you. Spec merged, and you have push access to this repo now.

[SevInf]

@siuying, why did you rolled back this commit?

[siuying]

@SevInf I'm sorry i made a mistake on this... I'm not intended to overwrite the commit

[siuying]

@SevInf Could you roll it back?

[SevInf]

Done. @siuying, actually you should never use push --force with a public repo with many contributors, such as this one. There may be some commits since you pulled last time, and they will completely disappear from history. It will be possible to recover them only if someone has this commits in their local repo.

[siuying]

@SevInf thanks. understood and noted carefully.