|
From: Oswald B. <os...@kd...> - 2005-04-08 19:10:55
|
moin, kde's cvs2svn migration is a few days ahead. i'm wondering, whether you guys want us to migrate the valgrind directory to the new repo. it seems pretty pointless to me, given that you have your own repo now and will lose the history since julian's fork anyway. it might make sense to keep the old cvs repo open for you as long as you do commits to the 2.4 branch (do you?), though. opinions? -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done. |
|
From: Julian S. <js...@ac...> - 2005-04-08 19:26:54
|
Hi Ossi. Yes, please do migrate it, since we need some place to put commits on the 2.4 branch, at least until 3.0 is available. Thanks, J On Friday 08 April 2005 20:10, Oswald Buddenhagen wrote: > moin, > > kde's cvs2svn migration is a few days ahead. i'm wondering, whether you > guys want us to migrate the valgrind directory to the new repo. it seems > pretty pointless to me, given that you have your own repo now and will > lose the history since julian's fork anyway. it might make sense to keep > the old cvs repo open for you as long as you do commits to the 2.4 > branch (do you?), though. > opinions? |
|
From: Oswald B. <os...@kd...> - 2005-04-08 19:32:05
|
On Fri, Apr 08, 2005 at 08:26:42PM +0100, Julian Seward wrote: > On Friday 08 April 2005 20:10, Oswald Buddenhagen wrote: > > it might make sense to keep the old cvs repo open for you as long as > > you do commits to the 2.4 branch (do you?), though. > > Yes, please do migrate it, since we need some place to put commits on > the 2.4 branch, at least until 3.0 is available. > find the mistake. ;) anyway, your decision. -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done. |