)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":6968,"name":"Christian Schwede","email":"cschwede@nvidia.com","username":"cschwede"},"change_message_id":"0b0057ad1f27f09df49176a96f3c9cafb16da945","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Kazuhiro MIYAHARA \u003cmiyahara.kazuhiro@lab.ntt.co.jp\u003e"},{"line_number":5,"context_line":"CommitDate: 2016-09-01 15:56:58 +0900"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Fix api referece of object GET request with Range pameter"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In RFC 7233, response body size of range requests with parameter \u0027bytes\u003dN-M\u0027"},{"line_number":10,"context_line":"is (M - N + 1). And Respose of object GET request with Range parameter in"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"fa7ab95a_ca3a29cd","line":7,"updated":"2016-09-01 13:12:00.000000000","message":"typos:\n \n referece -\u003e reference\n pameter -\u003e parameter","commit_id":"ca78bae8b7e644a3bf50514d2e5ff06b408df36b"},{"author":{"_account_id":6968,"name":"Christian Schwede","email":"cschwede@nvidia.com","username":"cschwede"},"change_message_id":"0b0057ad1f27f09df49176a96f3c9cafb16da945","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Fix api referece of object GET request with Range pameter"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In RFC 7233, response body size of range requests with parameter \u0027bytes\u003dN-M\u0027"},{"line_number":10,"context_line":"is (M - N + 1). And Respose of object GET request with Range parameter in"},{"line_number":11,"context_line":"current Swift implementation in according to the RFC.  However, in current"},{"line_number":12,"context_line":"api referece explains that responce body size of object GET request with"},{"line_number":13,"context_line":"\u0027Range: bytes\u003d10-15\u0027 is five( !\u003d 15 - 10 + 1)."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"fa7ab95a_ea3c4dc1","line":10,"updated":"2016-09-01 13:12:00.000000000","message":"typo:\n\n Respose -\u003e response","commit_id":"ca78bae8b7e644a3bf50514d2e5ff06b408df36b"},{"author":{"_account_id":12261,"name":"Mahati","email":"mahati.chamarthy@gmail.com","username":"Mahati"},"change_message_id":"f53680d97d9ee2460ced2f57dcb6b012aae8b421","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In RFC 7233, response body size of range requests with parameter \u0027bytes\u003dN-M\u0027"},{"line_number":10,"context_line":"is (M - N + 1). And Respose of object GET request with Range parameter in"},{"line_number":11,"context_line":"current Swift implementation in according to the RFC.  However, in current"},{"line_number":12,"context_line":"api referece explains that responce body size of object GET request with"},{"line_number":13,"context_line":"\u0027Range: bytes\u003d10-15\u0027 is five( !\u003d 15 - 10 + 1)."},{"line_number":14,"context_line":"This patch fixes the api reference explanation."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"fa7ab95a_ac20a89c","line":11,"updated":"2016-09-01 12:08:29.000000000","message":"nit: s/in/is","commit_id":"ca78bae8b7e644a3bf50514d2e5ff06b408df36b"},{"author":{"_account_id":12261,"name":"Mahati","email":"mahati.chamarthy@gmail.com","username":"Mahati"},"change_message_id":"f53680d97d9ee2460ced2f57dcb6b012aae8b421","unresolved":false,"context_lines":[{"line_number":9,"context_line":"In RFC 7233, response body size of range requests with parameter \u0027bytes\u003dN-M\u0027"},{"line_number":10,"context_line":"is (M - N + 1). And Respose of object GET request with Range parameter in"},{"line_number":11,"context_line":"current Swift implementation in according to the RFC.  However, in current"},{"line_number":12,"context_line":"api referece explains that responce body size of object GET request with"},{"line_number":13,"context_line":"\u0027Range: bytes\u003d10-15\u0027 is five( !\u003d 15 - 10 + 1)."},{"line_number":14,"context_line":"This patch fixes the api reference explanation."},{"line_number":15,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"fa7ab95a_2c3578d9","line":12,"updated":"2016-09-01 12:08:29.000000000","message":"nit: s/responce/response","commit_id":"ca78bae8b7e644a3bf50514d2e5ff06b408df36b"},{"author":{"_account_id":6968,"name":"Christian Schwede","email":"cschwede@nvidia.com","username":"cschwede"},"change_message_id":"0b0057ad1f27f09df49176a96f3c9cafb16da945","unresolved":false,"context_lines":[{"line_number":9,"context_line":"In RFC 7233, response body size of range requests with parameter \u0027bytes\u003dN-M\u0027"},{"line_number":10,"context_line":"is (M - N + 1). And Respose of object GET request with Range parameter in"},{"line_number":11,"context_line":"current Swift implementation in according to the RFC.  However, in current"},{"line_number":12,"context_line":"api referece explains that responce body size of object GET request with"},{"line_number":13,"context_line":"\u0027Range: bytes\u003d10-15\u0027 is five( !\u003d 15 - 10 + 1)."},{"line_number":14,"context_line":"This patch fixes the api reference explanation."},{"line_number":15,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"fa7ab95a_0a6331dd","line":12,"in_reply_to":"fa7ab95a_2c3578d9","updated":"2016-09-01 13:12:00.000000000","message":"typo:\n\n referece -\u003e reference","commit_id":"ca78bae8b7e644a3bf50514d2e5ff06b408df36b"}],"api-ref/source/parameters.yaml":[{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"9717921e94c9b29421153d21fc20d7eefb8c76e6","unresolved":false,"context_lines":[{"line_number":222,"context_line":"  required: true"},{"line_number":223,"context_line":"  type: string"},{"line_number":224,"context_line":"Range:"},{"line_number":225,"context_line":"  description: |"},{"line_number":226,"context_line":"    The ranges of content to get.  You can use the"},{"line_number":227,"context_line":"    ``Range`` header to get portions of data by using one or more"},{"line_number":228,"context_line":"    range specifications. To specify many ranges, separate the range"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"fa7ab95a_6c1da761","line":225,"updated":"2016-09-01 17:58:04.000000000","message":"Maybe this is too much scope creep, but...\n\nThis looks like crap on http://developer.openstack.org/api-ref/object-storage/index.html?expanded\u003dget-object-content-and-metadata-detail -- is there any way that we can add some newlines or something? It seems like we want something like\n\n\u003e The ranges of content to get. You can use the Range header to get portions of data by using one or more range specifications. To specify many ranges, separate the range specifications with a comma. The types of range specifications are:\n\u003e - Byte range specification. Use FIRST_BYTE_OFFSET to specify the start of the data range, and LAST_BYTE_OFFSET to specify the end. You can omit the LAST_BYTE_OFFSET and if you do, the value defaults to the offset of the last byte of data.\n\u003e - Suffix byte range specification. Use LENGTH bytes to specify the length of the data range.\n\u003e  \n\u003e The following forms of the header specify the following ranges of data:\n\u003e - Range: bytes\u003d-5. The last five bytes.\n\u003e - Range: bytes\u003d10-15. The five bytes of data after a 10-byte offset.\n\u003e - Range: bytes\u003d10-15,-5. A multi- part response that contains the last five bytes and the five bytes of data after a 10-byte offset. The Content-Type response header contains multipart/byteranges.\n\u003e - Range: bytes\u003d4-6. Bytes 4 to 6 inclusive.\n\u003e - Range: bytes\u003d2-2. Byte 2, the third byte of the data.\n\u003e - Range: bytes\u003d6-. Byte 6 and after.\n\u003e - Range: bytes\u003d1-3,2-5. A multi-part response that contains bytes 1 to 3 inclusive, and bytes 2 to 5 inclusive. The Content-Type response header contains multipart/byteranges.\n\nBut instead we currently get something closer to\n\n\u003e The ranges of content to get. You can use the Range header to get portions of data by using one or more range specifications. To specify many ranges, separate the range specifications with a comma. The types of range specifications are: - Byte range specification. Use FIRST_BYTE_OFFSET to specify the start of the data range, and LAST_BYTE_OFFSET to specify the end. You can omit the LAST_BYTE_OFFSET and if you do, the value defaults to the offset of the last byte of data. - Suffix byte range specification. Use LENGTH bytes to specify the length of the data range. The following forms of the header specify the following ranges of data: - Range: bytes\u003d-5. The last five bytes. - Range: bytes\u003d10-15. The five bytes of data after a 10-byte offset. - Range: bytes\u003d10-15,-5. A multi- part response that contains the last five bytes and the five bytes of data after a 10-byte offset. The Content-Type response header contains multipart/byteranges. - Range: bytes\u003d4-6. Bytes 4 to 6 inclusive. - Range: bytes\u003d2-2. Byte 2, the third byte of the data. - Range: bytes\u003d6-. Byte 6 and after. - Range: bytes\u003d1-3,2-5. A multi-part response that contains bytes 1 to 3 inclusive, and bytes 2 to 5 inclusive. The Content-Type response header contains multipart/byteranges.","commit_id":"ca78bae8b7e644a3bf50514d2e5ff06b408df36b"}]}