I would have never have picked up that one! Cheers.
On Tue, Jan 6, 2009 at 7:30 PM, <[email protected]> wrote: > Author: semor > Date: Tue Jan 6 19:30:55 2009 > New Revision: 8226 > > URL: http://svn.gna.org/viewcvs/relax?rev=8226&view=rev > Log: > Corrected a small typo in the development chapter of the manual. > > > Modified: > 1.3/docs/latex/develop.tex > > Modified: 1.3/docs/latex/develop.tex > URL: > http://svn.gna.org/viewcvs/relax/1.3/docs/latex/develop.tex?rev=8226&r1=8225&r2=8226&view=diff > ============================================================================== > --- 1.3/docs/latex/develop.tex (original) > +++ 1.3/docs/latex/develop.tex Tue Jan 6 19:30:55 2009 > @@ -415,7 +415,7 @@ > \subsubsection{Branch creation} > \index{repository!branch creation} > > -If a change is likely to be disruptive or cause breakages in the program, > the use of your own temporary branch is recommended. This private branch is > a complete copy of one of the main development lines wherein you can make > changes without disrupting the other developers. Although called a private > branch every change is visible to all other developers and each commit will > result in an automatic email to the relax-commits mailing list\index{mailing > list!relax-commits}. Other developers are even able to check out your branch > and make modifications to it. Private branches can also be used for testing > ideas. If the idea does not work the branch can be deleted from the > repository (in reality the branch will always exist between the revision > numbers of its creation and deletion and can always be resurrected). For > example to create a branch from the main 1.2 development line called > \texttt{molmol\_macros} whereby new Molmol macros are to be written, type > +If a change is likely to be disruptive or cause breakages in the program, > the use of your own temporary branch is recommended. This private branch is > a complete copy of one of the main development lines wherein you can make > changes without disrupting the other developers. Although called a private > branch every change is visible to all other developers and each commit will > result in an automatic email to the relax-commits mailing list\index{mailing > list!relax-commits}. Other developers are even able to check out your branch > and make modifications to it. Private branches can also be used for testing > ideas. If the idea does not work the branch can be deleted from the > repository (in reality the branch will always exist between the revision > numbers of its creation and deletion and can always be resurrected). For > example to create a branch from the main 1.3 development line called > \texttt{molmol\_macros} whereby new Molmol macros are to be written, type > > \begin{exampleenv} > \$ svn cp svn+ssh://[email protected]/svn/relax/1.3 $\backslash$ \\ > > > _______________________________________________ > relax (http://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://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
