Hmm....
strange.
I cannot see any updates via webcvs either.

However, cvs log malloc.c gives:

RCS file: /cvsroot/mspgcc/msp430-libc/src/stdlib/malloc.c,v
Working file: malloc.c
head: 1.3
branch:
locks: strict
access list:
symbolic names:
        RELENG_1: 1.2
        release_1: 1.1.1.1
        alpha1: 1.1.1.1
        start: 1.1.1.1
        vendor: 1.1.1
keyword substitution: kv
total revisions: 4;     selected revisions: 4
description:
----------------------------
revision 1.3
date: 2003/07/10 15:19:50;  author: diwil;  state: Exp;  lines: +4 -2
align bss_end to 2 bytes boundary
----------------------------
revision 1.2
date: 2002/05/07 12:13:58;  author: diwil;  state: Exp;  lines: +49 -47
many fixes mostly to float point library
----------------------------
revision 1.1
date: 2001/12/26 03:52:24;  author: cliechti;  state: Exp;
branches:  1.1.1;
Initial revision
----------------------------
revision 1.1.1.1
date: 2001/12/26 03:52:24;  author: cliechti;  state: Exp;  lines: +0 -0
initial upload
=============================================================================

well.... lets wait until SF updates.

~d




On Thursday 10 July 2003 20:44, Daniel Néri wrote:
> Steve Underwood <[email protected]> writes:
> > I just did a grab from CVS, and nothing seems to have changed in
> > libc.
>
> Anonymous CVS servers and ViewCVS are lagging w/ up to 24h (see SF.net
> site status page). On the other hand, I didn't see any commit message
> from Dmitry, and as you're a committer yourself, you should have
> access to up-to-date sources (via SSH).
>
>
> Regards,

-- 
/*****************************************************************
     ("`-''-/").___..--''"`-._     (\   Dimmy the Wild     UA1ACZ
      `6_ 6  )   `-.  (     ).`-.__.`)  State Polytechnical Univ.
      (_Y_.)'  ._   )  `._ `. ``-..-'   Radio-Physics Departament
    _..`--'_..-_/  /--'_.' ,'           Saint Petersburg,  Russia
   (il),-''  (li),'  ((!.-'             +7 (812) 5403923, 5585314
 *****************************************************************/


Reply via email to