> Only problem is that I have *just* changed the global structure to
> allow zak to be in the base, and I have not had time to transfer the
> files to the network-connected machine, which has been showing
> disk-rejection symptoms.  Will try now.
>

Hi John,

Has this been committed?  Last I checked a day or two ago I didn't see
anything new.

Thanks,
steven

I thpught it had been committed. 

Suffering a small hardware fault at present on the main Linux machine so 
hard to check.

Will see what I can do

==John

On Fri, 1 Aug 2003, steven yi wrote:

> > Only problem is that I have *just* changed the global structure to
> > allow zak to be in the base, and I have not had time to transfer the
> > files to the network-connected machine, which has been showing
> > disk-rejection symptoms.  Will try now.
> >
> 
> Hi John,
> 
> Has this been committed?  Last I checked a day or two ago I didn't see
> anything new.
> 
Well I see

(file) oload.c   1.2  7 days  jpff  Zak changes to global

so I did commit

My fault, I see the changes now too.  

Off to erase my source tree and grab the latest...

Thanks!

steven


On Sat, 2003-08-02 at 05:30, jpff@cs.bath.ac.uk wrote:
> On Fri, 1 Aug 2003, steven yi wrote:
> 
> > > Only problem is that I have *just* changed the global structure to
> > > allow zak to be in the base, and I have not had time to transfer the
> > > files to the network-connected machine, which has been showing
> > > disk-rejection symptoms.  Will try now.
> > >
> > 
> > Hi John,
> > 
> > Has this been committed?  Last I checked a day or two ago I didn't see
> > anything new.
> > 
> Well I see
> 
> (file) oload.c   1.2  7 days  jpff  Zak changes to global
> 
> so I did commit
> 
>