[PATCH] make bereq.uncacheable read-only outside backend_fetch

[Nils Goroll]

Writing to bereq.uncacheable in backend_response and backend_error would only
make sense in the context of a retry. In most real world cases, writing to
be*resp*.uncacheable would be intended in backend_response and backend_error.
---
 lib/libvcc/generate.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/libvcc/generate.py b/lib/libvcc/generate.py
index e82d610..0791671 100755
--- a/lib/libvcc/generate.py
+++ b/lib/libvcc/generate.py
@@ -360,7 +360,7 @@ sp_variables = [
        ('bereq.uncacheable',
                'BOOL',
                ( 'backend', ),
-               ( 'backend', ), """
+               ( 'backend_fetch', ), """
                Indicates whether the object requested from the backend is
                going to be uncacheable - either because the request was an
                explicit pass from the client side or a hit on an uncacheable
-- 
2.1.1