Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If you accidentally published sensitive info in that package you may want to contain the damage.


Then contact the people that run cargo.io and see if they are sympathetic and what options exist in the circumstances. Setting a sane standard of "no, you can't fuck up everybody that has depended on your public package" is a good thing.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: