I am not clear what is what would be called the maintainable source in the case of the ooo-site.
It is useful to know that some of the pages are generated automatically as byproducts of other processes (such as an IDL processor/generator) and are not the maintainable source. I wonder if there are places in the ooo-site publication staging- and tool-chain where one also must be careful not to patch downstream from the preferred source. Knowing there are other steps needed beyond committing working-copy changes to the ooo-site SVN is more mystery meat. The only way I have seen for triggering publishing of the site is on the CMS browser interface. I have no idea if that is the place for performing the missing step. - Dennis -----Original Message----- From: Jürgen Schmidt [mailto:[email protected]] Sent: Wednesday, February 08, 2012 23:59 To: [email protected] Subject: Re: [PATCH] fieldmaster Hi Joe, On 2/9/12 3:22 AM, Joe Schaefer wrote: > Well no, but the beauty of svn is that you only need > to deal with the section of the tree you are interested > in. So don't check-out all of ooo-site just to apply this > tiny patch- look at the patch to see which directory > it applies to and just check-out THAT. > > > Applying the patch is a matter of cd'ing to that > directory and running > > % patch< path/to/email/msg.txt > % svn commit -m 'apply fieldmaster patch' > I hope you can give me a hint what I am missing... I checked out http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/api some time ago and made some changes for example in the index.html (e.g. removed the project lead names) I checked the content locally and check in the index.html. But when I browse the API site my changes are not yet visible there. Which step is missing? Juergen > > ----- Original Message ----- >> From: Rob Weir<[email protected]> >> To: [email protected] >> Cc: >> Sent: Wednesday, February 8, 2012 9:17 PM >> Subject: Re: [PATCH] fieldmaster >> >> On Wed, Feb 8, 2012 at 3:22 PM, Joe Schaefer<[email protected]> >> wrote: >>> No idea if this is sufficient Ric, but I used the CMS >>> to email this patch as I explained earlier. >>> >> >> Cool. But unless we have more committers download ooo-site and set up >> an off-line site build environment, these patches are going to be slow >> to integrate. I'm guilty as well. I'll find some time to get this >> set up on my machine. >> >> Or is there any easier way to suck these patches into the CMS? For >> example, it would be really cool if there was an "upload/apply patch" >> button in the CMS "edit" view. That would enable any committer to >> review and apply site patches, even the ones not comfortable with SVN >> and command-line tools. >> >> -Rob >> >>> >>> >>> ----- Original Message ----- >>>> From: Joe Schaefer<[email protected]> >>>> To: [email protected] >>>> Cc: >>>> Sent: Wednesday, December 31, 1969 7:00 PM >>>> Subject: [PATCH] fieldmaster >>>> >>>> Here's the patch for Ric's issue. >>> ... >>> >>
