diff options
Diffstat (limited to 'doc/todo/bytes_in_privData__63__/comment_9_7c87ab0fba0aa90e2b24b457851b63c4._comment')
-rw-r--r-- | doc/todo/bytes_in_privData__63__/comment_9_7c87ab0fba0aa90e2b24b457851b63c4._comment | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/todo/bytes_in_privData__63__/comment_9_7c87ab0fba0aa90e2b24b457851b63c4._comment b/doc/todo/bytes_in_privData__63__/comment_9_7c87ab0fba0aa90e2b24b457851b63c4._comment new file mode 100644 index 00000000..b904351a --- /dev/null +++ b/doc/todo/bytes_in_privData__63__/comment_9_7c87ab0fba0aa90e2b24b457851b63c4._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 9""" + date="2016-06-17T01:33:05Z" + content=""" +Thank you, Andrew! + +Before I merge this, I want to clear up something that confuses me; +you characterized this as a bug that has bit you. How did the +pre-bytestring File.hasContentProtected exhibit buggy behavior? + +AFAICS, it already supported binary privdata, just in a suboptimal +way. + +(Also fileProperty and bytesProperty should indeed be deduped; +a second patch that merges them, even with an API change, would be ok.) +"""]] |