From: Mark M. <mie...@gm...> - 2010-02-25 20:15:41
|
Oh, okay. I was confused. <grin> I'll fix up anything that needs to done in the oodialog directory. -- Mark Miesfeld On Thu, Feb 25, 2010 at 12:07 PM, David Ashley <dav...@gm...> wrote: > Sorry, I left out that little detail. They were the 4.0.1 branch was > created from the 4.0.0 release. I then merged it with the docs trunk. > > Sorry about the confusion. > > David Ashley > > On 02/25/2010 01:27 PM, Mark Miesfeld wrote: >> David, >> >> This is the same message I sent to the svn notice. >> >> Hmm ... >> >> I'm not sure if I follow what you are doing here David. >> >> Shouldn't the 4.0.1 docs have been branched from the 4.0.0 release >> docs? Since there are no real changes in the bug fix, the docs should >> pretty much remain the same as the 4.0.0 release docs. >> >> There may have been a couple of doc fixes that could then be merged >> into 4.0.1, but there aren't many. >> >> -- >> Mark Miesfeld >> >> On Thu, Feb 25, 2010 at 11:23 AM, David Ashley >> <dav...@gm...> wrote: >> >>> Mark - take special note of this email. >>> >>> All - >>> >>> I created the 4.0.1 branch of the docs today. I then merged in the >>> changes from the docs trunk to that branch (except for oodialog - I will >>> leave that to you, Mark). I used the following scheme to perform the merge. >>> >>> 1. I did NOT modify the makefile! >>> 2. I merged each sgml file that had differences. I did NOT change the >>> graphics file names in the sgml files as I did not want to create a >>> large difference between the 4.0.0 and 4.0.1 docs. >>> 3. As far as I could tell there were no major additions to the docs I >>> merged, only editorial updates. >>> >>> So, except for oodialog, the docs are pretty much ready. >>> >>> David Ashley >>> >>> ------------------------------------------------------------------------------ >>> Download Intel® Parallel Studio Eval >>> Try the new software tools for yourself. Speed compiling, find bugs >>> proactively, and fine-tune applications for parallel performance. >>> See why Intel Parallel Studio got high marks during beta. >>> http://p.sf.net/sfu/intel-sw-dev >>> _______________________________________________ >>> Oorexx-devel mailing list >>> Oor...@li... >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> >>> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |