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

errors: new alias CURLE_WEIRD_SERVER_REPLY (8) #975

Closed
wants to merge 1 commit into from

Conversation

jay
Copy link
Member

@jay jay commented Aug 22, 2016

Since we're using CURLE_FTP_WEIRD_SERVER_REPLY in imap, pop3 and smtp as
more of a generic "failed to parse" introduce an alias without FTP in
the name.

Since we're using CURLE_FTP_WEIRD_SERVER_REPLY in imap, pop3 and smtp as
more of a generic "failed to parse" introduce an alias without FTP in
the name.
@jay
Copy link
Member Author

jay commented Aug 22, 2016

I'm not sure about the SDL file, whether I can use the same number twice. This will need a review from whoever handles VMS. Also @monnerat since I'm not sure if I can do the same in curl.inc.in

@bagder
Copy link
Member

bagder commented Aug 22, 2016

I'm in favor! But since we probably cannot see this as a bug-fix, I suggest we hold off and merge after the pending release.

@jay jay added the feature-window A merge of this requires an open feature window label Aug 22, 2016
@jay
Copy link
Member Author

jay commented Aug 22, 2016

ok

@monnerat
Copy link
Contributor

@jay: this should be perfect for OS400, you even did upgrade the ILE/RPG language interface. Many thanks.

@jay jay closed this in af2d679 Sep 8, 2016
@jay jay deleted the alias_errcode_8 branch September 19, 2016 20:04
@bagder bagder removed the feature-window A merge of this requires an open feature window label Sep 5, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Dec 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants