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
Generalize MutipartContent so that it can be used to replace MultipartRelatedContent #63
Comments
From yan...@google.com on March 27, 2012 07:22:33 Labels: Milestone-Version1.9.0 |
From rmis...@google.com on April 27, 2012 07:12:04 Requested by yanivi in http://codereview.appspot.com/6121048/diff2/1:2001/google-http-client/src/main/java/com/google/api/client/http/MultipartMixedContent.java Summary: Generalize MutipartContent so that it can be used to replace MultipartRelatedContent |
From rmis...@google.com on April 27, 2012 07:12:51 Labels: -Milestone-Version1.9.0 Milestone-Version1.10.0 |
From rmis...@google.com on May 24, 2012 05:37:58 Labels: -Milestone-Version1.10.0 Milestone-Version1.11.0 |
From yan...@google.com on July 14, 2012 04:35:17 Status: Accepted |
From yan...@google.com on August 02, 2012 05:13:28 Labels: -Milestone-Version1.11.0 |
From yan...@google.com on October 24, 2012 10:44:17 Labels: Milestone-Version1.13.0 Component-HTTP |
From rmis...@google.com on December 13, 2012 06:50:53 Labels: -Milestone-Version1.13.0 Milestone-Version1.14.0 |
From yan...@google.com on January 22, 2013 08:15:35 Owner: yan...@google.com |
From yan...@google.com on January 23, 2013 21:52:27 https://codereview.appspot.com/7199047/ Status: Started |
From yan...@google.com on February 01, 2013 04:47:06 Status: Fixed |
Make DefaultCredentialsProvider respect the CLOUDSDK_CONFIG environment variable.
From rmis...@google.com on January 31, 2012 15:15:45
Requested by yanivi in http://codereview.appspot.com/5539055/diff2/10001:18002/google-api-client/src/main/java/com/google/api/client/googleapis/batch/BatchRequest.java
Original issue: http://code.google.com/p/google-http-java-client/issues/detail?id=63
The text was updated successfully, but these errors were encountered: