[
https://issues.apache.org/jira/browse/COUCHDB-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13053719#comment-13053719
]
Marcello Nuccio commented on COUCHDB-941:
-
I add it here since I think it is non
On 23 Jun 2011, at 00:33, dav...@apache.org wrote:
Updated CHANGES and NEWS for all one people that build CouchDB on
Windows.
Heh...
I'm not entirely certain if the bug is in Chrome or how we expect
Chrome to react. I know there are browser differences when running
against localhost but I'm not entirely certain what they are and why.
I'll write a small test case in Python to try and reproduce and if so
will call it a Chrome bug
Reproduced a test case for this that fails on Chrome but passes on
Safari. Reported in the Chromium tracker as an extension of a very
similar bug:
http://code.google.com/p/chromium/issues/detail?id=79556
On Thu, Jun 23, 2011 at 9:54 AM, Paul Davis paul.joseph.da...@gmail.com wrote:
I'm not
Hi everyone,
As it’s known by many of you, Filipe and I have been working on improving
performance, specially write performance [1]. This work has been public in the
Couchbase github account since the beginning, and the non Couchbase specific
changes are now isolated in [2] and [3].
In [3]
Hi Damien, I'd like to see these 220 commits rebased into a set of logical
patches against trunk. It'll make the review easier and will help future devs
track down any bugs that are introduced. Best,
Adam
On Jun 23, 2011, at 6:49 PM, Damien Katz wrote:
Hi everyone,
As it’s known by
