I think having this history is of value; I had reason to look into the boulder-oracle-sprint branch only a couple of years ago.
If they're a nuisance, I suggest that we clone the Django repo into another one under the django organization -- say, "django-historical-branches" -- before removing them from the main repo. Shai. On Wednesday 24 February 2016 17:45:43 Tim Graham wrote: > Will anyone miss these branches if we remove them from the repository? I > presume they've all either been merged or are so outdated that there isn't > value in keeping them. > > attic/boulder-oracle-sprint > attic/full-history > attic/generic-auth > attic/gis > attic/i18n > attic/magic-removal > attic/multi-auth > attic/multiple-db-support > attic/new-admin > attic/newforms-admin > attic/per-object-permissions > attic/queryset-refactor > attic/schema-evolution > attic/schema-evolution-ng > attic/search-api > attic/sqlalchemy > attic/unicode > soc2009/admin-ui > soc2009/http-wsgi-improvements > soc2009/i18n-improvements > soc2009/model-validation > soc2009/multidb > soc2009/test-improvements > soc2010/app-loading > soc2010/query-refactor > soc2010/test-refactor
