Follow-up Comment #2, sr #104708 (project administration):
Hrm. ftp.gnu.org/non-gnu/cvs is already a mirror of Savannah in this case.
I'm not sure how the current mirroring setup would interoperate with also
using the ftp.gnu.org interface.
The easiest thing from my end would be if you let me create and admin
download directories on Savannah, let other project members do the same, and
the current mirroring script continued to mirror this to ftp.gnu.org, but
perhaps the best thing all around would be if I and any project members who
wish to registered to admin the ftp.gnu.org/non-gnu/cvs directory directly
and we broke the mirror? This would avoid the ~4 hour delay between uploads
to Savannah and the mirroring, and I could then avoid advertising the
Savannah download page in release announcements, which should save on
Savannah bandwidth. We could also leave the binaries off Savannah which
should also save Savannah bandwidth and you wouldn't have to hurry with any
Savannah download subdir admin programs. In the end, this wouldn't be much
harder for me anyhow, since my release uploads are scripted anyhow - I'll
only have to make the change once.
Are we agreed? If so, I can send the appropriate requests to
[EMAIL PROTECTED]
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/support/?func=detailitem&item_id=104708>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Savannah-help-public mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/savannah-hackers
