[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: capabilities and client ids
|
From: |
Neal H. Walfield |
|
Subject: |
Re: capabilities and client ids |
|
Date: |
Thu, 02 Dec 2004 17:44:37 +0000 |
|
User-agent: |
Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.2 (i386-debian-linux-gnu) MULE/5.0 (SAKAKI) |
> However, it does mean that we can unify the client entry
> (_hurd_cap_client_entry_t) and client (_hurd_cap_client_t) data
> structures thereby eliminating a level of indirection. The attached
> patch does this. Let me know if it is all right.
>
> 2004-12-01 Neal H. Walfield <address@hidden>
>
> * cap-server-intern.h (struct _hurd_cap_client): Fold the struct
> _hurd_cap_client_entry into the struct _hurd_cap_client.
> * bucket-create.c (_hurd_cap_client_death): Change all uses of
> _hurd_cap_client_entry_t to use the merged _hurd_cap_client_t.
> (hurd_cap_bucket_create): Likewise.
> * bucket-manage-mt.c (lookup_client): Likewise.
> * client-create.c (_hurd_cap_client_create): Likewise.
> * client-release.c (_hurd_cap_client_release): Likewise.
Based on private discussion with marcus, I have checked this in.