<br><br><div><span class="gmail_quote">On 9/28/05, <b class="gmail_sendername">Rafael Laboissiere</b> <<a href="mailto:rafael@debian.org">rafael@debian.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* Colin Ingram <<a href="mailto:synergizedmusic@gmail.com">synergizedmusic@gmail.com</a>> [2005-09-28 09:48]:<br><br>> Since working on 2.9 is the main reason I joined I would love to take<br>> this task on.<br>
<br><br>Please notice that both octave2.1 and octave2.9 are in a single SVN<br>module, namely <a href="svn://svn.debian.org/svn/pkg-octave/trunk/packages/octave/">svn://svn.debian.org/svn/pkg-octave/trunk/packages/octave/
</a>.<br><br>The entries in debian/changelog alternate between both versions. It is<br>done this way on purpose.</blockquote><div><br>
Just for the clarification:<br>
<br>
The point of this is to ensure there is a common build
infrastructure? As such, a necessary consquence is that any
changes I make should not break 2.1 as they will be included in new
releases of the 2.1 branch. Therefore I should test my changes on
the 2.1 source as well as the 2.9?<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Good luck,</blockquote><div><br>
<br>
Thanks <br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">--<br>Rafael<br><br>_______________________________________________<br>Pkg-octave-devel mailing list
<br><a href="mailto:Pkg-octave-devel@lists.alioth.debian.org">Pkg-octave-devel@lists.alioth.debian.org</a><br><a href="http://lists.alioth.debian.org/mailman/listinfo/pkg-octave-devel">http://lists.alioth.debian.org/mailman/listinfo/pkg-octave-devel
</a><br></blockquote></div><br>