thanks for the time you taken to explain (in perfect English). The link you provided is no longer working but I will google for and read subversion for writer (and similar). I would still like a bullet list of actions too though if anyone is reading :) e.g.. from the point of having set up and have a working beanstalk account with repository and working copy (i.e all good from one location) set up versions on a second location & connection to you projects beanstalk account then...
I'm thinking it's something like this...(please correct areas in ? or let me know if i have it all wrong - totally possible) 1: update/ checkout? on your 2nd computer 2: edit in your fav editor 3: commit from your second computer 4: go to 1st computer and update / checkout? repeat step 1 on your first computer etc... thanks all, pSouper On Mar 29, 12:51 pm, "Rolf Schmolling M.A." <[email protected]> wrote: > Hi, > > your questions (please excuse my limited English) concern the very basic > workings of versioning. So I suggest you familiarize yourself with the > concept. I am no programmer myself and keep my dissertation project under > version control (e.g. subversion). For me this link was quite helpful to get > started: > > http://strangenoises.org/subversion-for-writers/ > > Your beanstalk account is basically a central storing place. When "chekin' > out" you get a copy on your computer to work with. Any change then needs to > be put back and _merged_ with the online version at beanstalk. You (or any > colleagues) can have other _versions_ of that central suppository (the > storing place) e.g. _working copies_. If you change things in one of your > working copies and DIFFERENT changes on the OTHER working copies, _checking > in_ means that there will be a CONFLICT to be resolved. Subversion gives you > the ability to control all this, and Versions is a program to enable working > with this via a nice GUI (with limits, e.g. merge). > > Hope that gets you started, > > Regards, > > Rolf > > Am 29.03.2011 um 10:33 schrieb pSouper: > > > Hi all, > > would anyone be able to explain the process of working on the same > > project from two locations using versions and beanstalk. > > > I have a home and work mac, I have two versionsapp's, I have one > > beanstalkapp account. I would like to 'upload' changes from work to > > beanstalk, download these changes at home, add, edit & delete then > > upload the files again ready for download again at work. > > > I would have though check-in/out is the way to go but 'update' & > > 'commit' also do things that look similar so i have a few Q's... > > > what does update do (in my case)? does it check beanstalk for any > > changes that have been made from commits not on this machine or does > > it just rescan the working folders for changes as refresh the list? > > > what does checkout do? Does it lock the beanstalkapp file preventing > > it from being changes or commited over by another machine until i > > check it in again? also.. does it first check for & download the > > latest version from beanstalkapp then lock it? > > > Is there an n.bullet-point 'work-flow' for using versions > > collaboratively from two locations? or would anyone have a few mins to > > know one up and free my mind of the deamons please? > > > all help greatly appreciated. > > pSouper > > > -- > > You received this message because you are subscribed to the Google Groups > > "Versions" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/versions?hl=en. -- You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
