Keeping a local CVS repository updated with public CVS changes...

[law@redhat.com]

In message <200202142350.SAA02674@iron.>, apl@alum.mit.edu writes:
 > I like to have my own private CVS repository where I can checkin
 > work-in-progress and insure a stable working version without daily
 > changes - and for example, if I experiment with changing something
 > like
 > 
 > 	gcc/expr.c
 > 
 > I can just
 > 
 >       rm expr.c
 >       cvs update expr.c
 > 
 > and get back one that's known to be identical with what I started
 > with.
I'm pretty sure CVSup can do what you want.

jeff