Re: git branch strategy after 1.11

2009-03-24 Thread Ralf Wildenhues
* Jan Engelhardt wrote on Tue, Mar 24, 2009 at 11:01:02PM CET: > On Tuesday 2009-03-24 22:48, Ralf Wildenhues wrote: > > > >> And: once branch-1.11 development finally ceases, it can be deleted. > >> This works because the commits remain reachable via the release tags. > >> If necessary, the branch

Re: git branch strategy after 1.11

2009-03-24 Thread Jan Engelhardt
Hi Ralf, On Tuesday 2009-03-24 22:48, Ralf Wildenhues wrote: > >> And: once branch-1.11 development finally ceases, it can be deleted. >> This works because the commits remain reachable via the release tags. >> If necessary, the branch pointer can simply be recreated. > >What would be the advanta

Re: git branch strategy after 1.11

2009-03-24 Thread Ralf Wildenhues
Hi Jan, * Jan Engelhardt wrote on Tue, Mar 24, 2009 at 08:56:08AM CET: > On Sunday 2009-03-22 12:23, Ralf Wildenhues wrote: > > > >just to let you know, after 1.11 I intend to change the branch setup a > >bit. When branch-1-11 is created, I will also create a branch maint, > >which will then rece

Re: git branch strategy after 1.11

2009-03-24 Thread Jan Engelhardt
On Sunday 2009-03-22 12:23, Ralf Wildenhues wrote: >Hello everyone, > >just to let you know, after 1.11 I intend to change the branch setup a >bit. When branch-1-11 is created, I will also create a branch maint, >which will then receive bug fixes appropriate for both 1.11.x and 1.11a. >The maint

git branch strategy after 1.11

2009-03-22 Thread Ralf Wildenhues
Hello everyone, just to let you know, after 1.11 I intend to change the branch setup a bit. When branch-1-11 is created, I will also create a branch maint, which will then receive bug fixes appropriate for both 1.11.x and 1.11a. The maint branch will then be merged regularly (most likely after ev