Re: remove old SVN branches from git repository?

[Tim Graham]

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 git replace 
 has been 
added." I don't know if that might allow deleting the branches? Anyway, if 
anyone wants to take some action here that's okay with me as I'm not really 
motivated to invest any more time than clicking "delete branch" which 
apparently isn't acceptable at this time.

On Wednesday, February 24, 2016 at 7:13:55 PM UTC-5, Markus Holtermann 
wrote:
>
> 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 call `git remote prune upstream`. 
> The branches in the remotes should still be available. 
>
> /Markus 
>
> On Wed, Feb 24, 2016 at 12:46:38PM -0800, Tim Graham wrote: 
> >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 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 suggest the same :D 
> >> 
> > 
> >-- 
> >You received this message because you are subscribed to the Google Groups 
> "Django developers  (Contributions to Django itself)" group. 
> >To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-develop...@googlegroups.com . 
> >To post to this group, send email to django-d...@googlegroups.com 
> . 
> >Visit this group at https://groups.google.com/group/django-developers. 
> >To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/ffceaa3b-ae34-4d2f-8ea2-7fa382b94a30%40googlegroups.com.
>  
>
> >For more options, visit https://groups.google.com/d/optout. 
>
>
> -- 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/a631d527-bd54-4234-9148-ae519865bfe9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: remove old SVN branches from git repository?

[Markus Holtermann]

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 call `git remote prune upstream`.
The branches in the remotes should still be available.

/Markus

On Wed, Feb 24, 2016 at 12:46:38PM -0800, Tim Graham wrote:

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 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 suggest the same :D



--
You received this message because you are subscribed to the Google Groups "Django 
developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/ffceaa3b-ae34-4d2f-8ea2-7fa382b94a30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

--
You received this message because you are subscribed to the Google Groups "Django 
developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/20160225001335.GA3849%40pyler.local.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: remove old SVN branches from git repository?

[Shai Berger]

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?

[Tim Graham]

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 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 suggest the same :D
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/ffceaa3b-ae34-4d2f-8ea2-7fa382b94a30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: remove old SVN branches from git repository?

[Florian Apolloner]

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 suggest the same :D

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/a1cd51c0-446a-46fc-ad7c-b81b7472f3a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: remove old SVN branches from git repository?

[Shai Berger]

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

remove old SVN branches from git repository?

[Tim Graham]

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/e194a366-324c-4265-9322-7bacd623f423%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.