On Sunday 19 Dec 2010 20:33:05 Christian Stimming wrote:
> Am Sonntag, 19. Dezember 2010 schrieb Mike Evans:
> > On Saturday 18 Dec 2010 16:33:59 Phil Longstaff wrote:
> > > I will be creating the 2.4.0 tarballs this weekend. Please don't check
> > > in any changes unless they are absolutely criti
Am Sonntag, 19. Dezember 2010 schrieb Mike Evans:
> On Saturday 18 Dec 2010 16:33:59 Phil Longstaff wrote:
> > I will be creating the 2.4.0 tarballs this weekend. Please don't check
> > in any changes unless they are absolutely critical.
> >
> > Derek, is there any way to lock the tree so I can m
On Saturday 18 Dec 2010 16:33:59 Phil Longstaff wrote:
> I will be creating the 2.4.0 tarballs this weekend. Please don't check
> in any changes unless they are absolutely critical.
>
> Derek, is there any way to lock the tree so I can make 2.4.0 without any
> danger of checkins inadvertently des
On 10-12-18 10:33 AM, Phil Longstaff wrote:
I will be creating the 2.4.0 tarballs this weekend. Please don't check
in any changes unless they are absolutely critical.
Derek, is there any way to lock the tree so I can make 2.4.0 without any
danger of checkins inadvertently destabilizing the co
Am Samstag, 18. Dezember 2010 schrieb Phil Longstaff:
> I will be creating the 2.4.0 tarballs this weekend. Please don't check
> in any changes unless they are absolutely critical.
>
> Derek, is there any way to lock the tree so I can make 2.4.0 without any
> danger of checkins inadvertently dest
On Sat, December 18, 2010 11:33 am, Phil Longstaff wrote:
> I will be creating the 2.4.0 tarballs this weekend. Please don't check
> in any changes unless they are absolutely critical.
>
> Derek, is there any way to lock the tree so I can make 2.4.0 without any
> danger of checkins inadvertently d
I will be creating the 2.4.0 tarballs this weekend. Please don't check
in any changes unless they are absolutely critical.
Derek, is there any way to lock the tree so I can make 2.4.0 without any
danger of checkins inadvertently destabilizing the code?
Phil
_