Cleanup of old remote branches

Hi internals. Doing a git branch --all , I notice that we still carry very old branches (back from the svn or even cvs times). Here is the list : remotes/origin/experimental/5.2-WITH_DRCP remotes/origin/experimental/5.3-FPM remotes/origin/experimental/RETURN_REF remotes/origin/experimental/ZendEngine2 remotes/origin/experimental/apache_hooks remotes/origin/experimental/first_unicode_implementation remotes/origin/experimental/lemon remotes/origin/experimental/namespaces remotes/origin/experimental/new_apache_hooks remotes/origin/experimental/new_ui_api remotes/origin/experimental/newoperator remotes/origin/experimental/phar_tar remotes/origin/experimental/pre_new_hash_func remotes/origin/experimental/rand_redesign remotes/origin/experimental/the_5_4_that_isnt_5_4 remotes/origin/experimental/threaded remotes/origin/experimental/with_scalar_types remotes/origin/experimental/zts_stdc_scanners remotes/origin/experimetnal/RETURN_REF_PATCH remotes/origin/immutable-date remotes/origin/master remotes/origin/migration/EXPERIMENTAL remotes/origin/migration/INITIAL remotes/origin/migration/RELEASE_1_0_0 remotes/origin/migration/sqlite-start remotes/origin/migration/unlabaled-1.1.2 remotes/origin/migration/unlabaled-1.29.2 remotes/origin/migration/unlabaled-1.3.2 remotes/origin/migration/unlabaled-1.67.2 We don't need git space, right ; but I think we need some cleanup to keep consistency. While I know "immutable-date" or even "lemon" could still be reworked on in the future, I personnaly have absolutely no clue about "migration/unlabaled-1.67.2" for example. "experimental/the_5_4_that_isnt_5_4" is funny as well, I guess it's a try for someone, I haven't diffed it anyway. I assume some of our remote branches are both old and useless nowadays. Could we make a list of the remote branches we really don't need anymore, and clean them up ? Thx Julien Pauli