> How about pre-announce a planned deletion some months ahead, give people > time to migrate off
If the repository has been cloned, are there any operations that require the remote? We could leave the old mirror there to be polled for updates- which it will never have- but I was under the impression that a cloned git repo was independent. Nobody should clone the old mirror if they're starting anew, so I'd rather just delete it than confuse people who reasonably expect "hadoop.git" to contain a current version, pull down something that appears to contain core, mapred, and hdfs, and then need to migrate their work to the active repositories. -C
