I can appreciate that, which is why I'm making a friendly suggestion about their worflow that will induce less overall churn in svn. I certainly didn't expect them to figure this all out by themselves ;-).
>________________________________ > From: Dave Fisher <[email protected]> >To: [email protected] >Sent: Wednesday, April 4, 2012 12:47 PM >Subject: Re: svn commit: r811513 - in /websites/production/ooo-site: cgi-bin/ >content/ > >Hi Joe, > >This person is trying to hack a translation on top of the banner and topnav. >They are trying to learn by doing. > >They just learned how to publish yesterday. > >I've pointed them at the proper way to engage the SSI setup in a response to >r1309306. I hope that they engage. > >Regards, >Dave > >On Apr 4, 2012, at 9:36 AM, Joe Schaefer wrote: > >> I see you are making lots of incremental changes >> and publishing each one individually. Have you >> considered making better use of the staging site >> to view the live results of your commits, and iterating >> on the commits before publishing the final results? >> >> >> >> >>> ________________________________ >>> From: "[email protected]" <[email protected]> >>> To: [email protected] >>> Sent: Wednesday, April 4, 2012 12:34 PM >>> Subject: svn commit: r811513 - in /websites/production/ooo-site: cgi-bin/ >>> content/ >>> >>> Author: bidouille >>> Date: Wed Apr 4 16:34:24 2012 >>> New Revision: 811513 >>> >>> Log: >>> Publishing svnmucc operation to ooo-site site by bidouille >>> >>> Added: >>> websites/production/ooo-site/cgi-bin/ >>> - copied from r811512, websites/staging/ooo-site/trunk/cgi-bin/ >>> websites/production/ooo-site/content/ >>> - copied from r811512, websites/staging/ooo-site/trunk/content/ >>> >>> >>> > > > >
