🚀 go-pugleaf

>>>>> yee@mipgsun.mipg.upenn.edu (Conway Yee) said:

Conway> yee@mipgsun.mipg.upenn.edu (Conway Yee) writes:
>RCS and CVS will not work with ftp.  FSF maintains a ftp archive site.
>Most users of the archive site does not have accounts on FSF machines.

Conway> coolidge@apple.com writes:
>RCS works great with ftp. On each major version release, include the RCS
>files back to version x.0. Alternatively, simply make available an RCS
>file that runs you back to x.0. 

Conway> I take it then, that by "works great" you mean that the FSF should
Conway> distribute a RCS directory tree which contains EVERYTHING.  That way,
Conway> the ftp'er must untar the file and then check out the version that he
Conway> wants.  Is this practical?  As it stands right now, the FSF does not
Conway> provide diff's for some releases because the diff file would simply be
Conway> too large.  To distribute a RCS file which contains diffs back to the
Conway> first release of a package would be prohibitive.

Conway> When I wrote that RCS will not work with ftp, I meant that it is a ftp
Conway> user can not ftp gcc version 1.15 (or some such) directly from the gcc
Conway> RCS source tree.  Isn't this the case?

What you could do is set up an E-mail server which would get things
for you. For instance:

The message: