I see these branches are documented:
https://docs.djangoproject.com/en/dev/internals/git/#feature-development-branches.
In reading that I saw the mention about a grafts file. I don't entirely
understand what that does but when I was reading about it, I saw "As of Git
1.6.5, the more flexible
I'd like to keep them around somewhere. Even if it's just a wiki page
which links to the last commits of each branch.
When you have a local checkout of a brach that checkout is staying even
if the branch is removed on a remote. Also your local references to
remote branches are kept unless you
On Wednesday 24 February 2016 22:46:38 Tim Graham wrote:
> They're already in everyone's forks too unless you delete them.
True, but I think we should keep them accessible under the project roof.
Shai.
They're already in everyone's forks too unless you delete them. Not sure if
deleting them from the main repo would delete them for all forks too.
On Wednesday, February 24, 2016 at 3:36:53 PM UTC-5, Florian Apolloner
wrote:
>
>
>
> On Wednesday, February 24, 2016 at 9:12:19 PM UTC+1, Shai
On Wednesday, February 24, 2016 at 9:12:19 PM UTC+1, Shai Berger wrote:
>
> 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.
>
I was about to
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
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
