Merge request: object locks

Tom Lord <lord-1tv/[email protected]> writes:

>     >> From: Andreas Rottmann <[email protected]>
>
>     >> I've started porting the GLib memchunk implementationn to
>     >> hackerlab. 
>
>     > Why?
>
> (I am merging in your hashtree_fold, though.)
>
Fine. If you've done that, you should be ready to merge the object
lock and object data area stuff from my pika-scm--integration branch
(patch-14 -- patch-16).

BTW: I'd like to make the current revision of my hackerlab category a
new branch (named memchunks), and revert the --devo--1.0 branch to be
without memchunks, so you can star-merge it without problems. Is the
following "OK"?

% tla tree-version
a.rottmann-w/4MtoFGNSSxwFGv/1/[email protected]/hackerlab--devo--1.0
% tla revisions -s
base-0
    tag of [email protected]/hackerlab--devo--1.0--patch-39
patch-1
    Put mem-chunk interface in place
patch-2
    Added hashtree_fold()
patch-3
    A bit of mem-chunk documentation
patch-4
    ported GLib memchunk implementation, added memchunk unit test
patch-5
    fsplay_raise() bugfix
patch-6
    memchunk work
% tla archive-setup hackerlab--memchunks--0.1
% tla tag hackerlab--devo--1.0 hackerlab--memchunks--0.1
% for x in 1 3 5 6; do 
    tla replay --reverse hackerlab--devo--1.0--patch-$x
  done
% tla commit -L 'reverted memchunk stuff'

Andy
-- 
Andreas Rottmann         | [email protected]      | [email protected] | [email protected]
http://yi.org/rotty      | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62

It's *GNU*/Linux dammit!