This is done now. All of the branches were fully merged except for v1.1.x
which had a single line change to contents.rst which ended up on the main
branch through other means.
I have local branches pointing to all of the removed branches so if there
is panic about their removal and _everyone_ run
On 2014/11/01, 5:49 AM, Thomas Caswell wrote:
> Does anyone protest to removing all of the branches from the main repo
> except:
>
> - master
> - v1.4.x
> - v1.4.2-doc
>
> Having old branches around can lead to confusion (see
> https://github.com/matplotlib/matplotlib/pull/3748#issuecomment-6
I think this is reasonable. If anything, I *might* want to keep N+1
branches, but that might be too much.
On Sat, Nov 1, 2014 at 12:31 PM, Joel B. Mohler
wrote:
> On 11/01/2014 11:49 AM, Thomas Caswell wrote:
> > Does anyone protest to removing all of the branches from the main repo
> > except:
On 11/01/2014 11:49 AM, Thomas Caswell wrote:
> Does anyone protest to removing all of the branches from the main repo
> except:
>
> - master
> - v1.4.x
> - v1.4.2-doc
>
As a person who was distracted by too many branches in that list, I
fully support this.
Joel
Todd,
The tags would not go anywhere, just the branches would be removed.
The tags are for releases, branches are for active work and there should be
no active work on anything but those three branches.
Tom
On Sat, Nov 1, 2014, 12:14 Todd wrote:
>
> On Nov 1, 2014 4:49 PM, "Thomas Caswell" w
On Nov 1, 2014 4:49 PM, "Thomas Caswell" wrote:
>
> Does anyone protest to removing all of the branches from the main repo
except:
>
> - master
> - v1.4.x
> - v1.4.2-doc
>
> Having old branches around can lead to confusion (see
https://github.com/matplotlib/matplotlib/pull/3748#issuecomment-613
Does anyone protest to removing all of the branches from the main repo
except:
- master
- v1.4.x
- v1.4.2-doc
Having old branches around can lead to confusion (see
https://github.com/matplotlib/matplotlib/pull/3748#issuecomment-61372162).
Tom
--
