Hi Troels, I know I was on holidays, but please discuss on the development mailing list before merging a branch back to trunk. You have the ability to do this, but it would be very useful to have the code carefully checked by another relax developer for consistency and other issues before it is merged. For example there may be changes that were developed for this analysis that are incompatible with one of the other relax analyses, even if it is not caught in the test suite. I would prefer to clear the code for merging first.
Cheers, Edward On 14 August 2014 10:53, <[email protected]> wrote: > Author: tlinnet > Date: Thu Aug 14 10:53:34 2014 > New Revision: 25019 > > URL: http://svn.gna.org/viewcvs/relax?rev=25019&view=rev > Log: > Initialized merge tracking via "svnmerge" with revisions "1-24916" from > svn+ssh://[email protected]/svn/relax/branches/R1_fitting > > Modified: > trunk/ (props changed) > > Propchange: trunk/ > ------------------------------------------------------------------------------ > svnmerge-integrated = /branches/R1_fitting:1-24916 > > > _______________________________________________ > relax (http://www.nmr-relax.com) > > This is the relax-commits mailing list > [email protected] > > To unsubscribe from this list, get a password > reminder, or change your subscription options, > visit the list information page at > https://mail.gna.org/listinfo/relax-commits _______________________________________________ relax (http://www.nmr-relax.com) This is the relax-devel mailing list [email protected] To unsubscribe from this list, get a password reminder, or change your subscription options, visit the list information page at https://mail.gna.org/listinfo/relax-devel
