From: William S F. <ws...@fu...> - 2012-05-07 19:15:22
|
Vincent For all the other GSoC branches, I have been updating the old branches to nearly the trunk HEAD - actually to swig-2.0.6 (rev 13025 on trunk). As you have been merging trunk quite often to gsoc2009-sploving, could you please do one final merge from trunk to this branch. Then can you create a branch from the HEAD of gsoc2009-sploving and call it gsoc2012-scilab ready for Wolfgang to start GSoC 2012. Thanks William On 02/05/12 13:53, Vincent COUVERT wrote: > The problem is that I have to merge too branches to get the trunk > modifications into the gsoc2012-branch but I agree it is not so > difficult and it is better to make the student modifications visible. > > Ok for me to create a new branch from gsoc2009-sploving and following > the standard way. > > Regards, > Vincent > > Le 02/05/12 11:38, Vadim Zeitlin a écrit : >> On Wed, 02 May 2012 10:24:38 +0200 Vincent COUVERT<vin...@sc...> wrote: >> >> VC> Since the gsoc2009-sploving is not stable yet and some functionalities >> VC> are missing in it, I think that Wolfgang will first have to complete the >> VC> on-going work in this development branch so I would prefer to keep this >> VC> single branch for Scilab even if it is not the standard way to go. >> >> Hello, >> >> GSoC rules require that the student work be easily visible/available and >> the simplest way to ensure that it is is to do all of it on a branch. It >> doesn't matter if you start this branch from the trunk or from another >> existing branch but you really should have it. >> >> What exactly is the problem with branching gsoc2012-whatever from the >> current tip of gsoc2009-sploving? It would, of course, be preferable to >> merge with the trunk first so that the branches don't diverge too far but >> if you don't want/can't do this, you can still create a new branch from >> this one, I really don't see how could it possibly inconvenience anybody? >> >> Regards, >> VZ > |