Re: remove old SVN branches from git repository?

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

Re: remove old SVN branches from git repository?

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.

Re: remove old SVN branches from git repository?

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

Re: remove old SVN branches from git repository?

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

Re: remove old SVN branches from git repository?

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

remove old SVN branches from git repository?

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

Re: Logged out sessions are resurrected by concurrent requests (ticket 21608)

You could ask a friend or colleague to review the patch using the patch review checklist [1] and mark it "Ready for checkin" if it looks good. Otherwise, you just wait for someone to review it. [1]

Re: Logged out sessions are resurrected by concurrent requests (ticket 21608)

Is there something I can do to move this forward? Den torsdag 11 februari 2016 kl. 09:56:15 UTC+1 skrev Tore Lundqvist: > > Thanks for all the help with the patch! I hope its close to being > acceptable now. Can someone have a look at the PR? > > Den tisdag 2 februari 2016 kl. 13:08:51 UTC+1

Re: Help! ImportError: No module named ...

On Wed, Feb 24, 2016, Damián LLuch Castelli wrote: >Hi, It is the first time I write here. Sorry for the beginner question. This is not the correct place for questions like this. You'll get answers to questions like this on the django-users email list,

Help! ImportError: No module named ...

Hi, It is the first time I write here. Sorry for the beginner question. I was doing the next tutorial in python and I appeared this error. http://www.marinamele.com/taskbuster-django-tutorial/settings-different-environments-version-control (prueba3)

Re: Feature proposal: selection of views and tables for inspectdb

If inspectdb had exception handling as proposed in https://code.djangoproject.com/ticket/14098#comment:8 would that solve the issue? On Wednesday, February 3, 2016 at 5:00:36 PM UTC-5, José Tomás Tocino wrote: > > Sorry I've been pretty disconnected from this thread. > > The TL;DR version of