[4633] in SIPB bug reports
Re: Supporting /afs/sipb/project/gnu
daemon@ATHENA.MIT.EDU (yandros@MIT.EDU)
Sun Jun 19 02:19:27 1994
From: yandros@MIT.EDU
Date: Sun, 19 Jun 94 02:19:16 -0400
To: ghudson@MIT.EDU
Cc: bug-sipb@MIT.EDU, bug-outland@MIT.EDU, sipb-gnu@MIT.EDU, jfc@MIT.EDU
In-Reply-To: <m0qF5Kb-0004KYC@glacier> (ghudson@MIT.EDU)
I think that what I'd like to see is the `gnu' filsys point to the
filsys group containing /afs/sipb.mit.edu/project/gnu and
/afs/athena.mit.edu/project/gnu (or contrib/gnu), with the sipb copy
as the primary, synctree'd into the athena copy each night. This
seems to work well for the sipb locker. The support issue isn't a
concern to me, since we can (and should, IMHO) still maintain the
party line ``the supported version of {gcc,g++,gdb} is in the cygnus
locker''
`blanche -m gnu' shows that most of the `maintainers' are SIPB
members. No one ever does anything with the locker; the cygnus locker
is the official response to the gnu locker needing a maintainer. The
gnu locker as it exists is only there to confuse people. Can anyone
think of a reason not to just remove the whole thing and start over?
