Inconsistance in snapshots repository

[Jeffrey A Law]

  In message < 199804171629.JAA04146@atrus.synopsys.com >you write:
  > In message < 199804162331.TAA25018@melange.gnu.org >you write:
  > >   > I'm CVS-unaware, but, generally, is this really guaranteed to provide
  > >   > a coherent snapshot to anyone, anytime, including if they try using
  > >   > it while a snapshot is being produced (and the "moving tag" updated)?
  > > Nope.  But what it does do for the CVS folks is allow them to 
  > > upgrade to whatever the current snapshot happens to be without
  > > knowing the exact name of the tag.
  > 
  > Ah, but it seems like a lot of work.  How about
  > 
  > finger latest-egcs-snapshot@cygnus.com
  > 
  > to find that out?  It certainly would be more robust.
Actually, it turns out the cvs command posted to this group will
do the right thing.

So, at the time I make the snapshot available I just issue the magic
CVS command, and in 2-5 minutes the "latest snapshot" tag is in
place.

Folks can then check out the tree using a sticky tag, later "cvs update"
operations will only change things if there's been a newer snapshot
made.

jeff