Thanks! This will be a big help.
On 3/2/06 6:43 PM, "Jeff Abbott" <[EMAIL PROTECTED]> wrote: > The best CVS resource I've found -- other than knowledgeable people > such as this list -- is the CVS Book. It's available for free at: > > http://cvsbook.red-bean.com/ > > It looks like they've recently changed it and got it published, so > now it's a PDF, but I took a cursory look through it and it still has > the same good information. I'd read through CVS Basics starting on > page 17 and A Tour of CVS starting on page 25 to get a good idea of > what you'll be dealing with. > > The basic idea behind is that somewhere out there is your CVS > repository, most likely stored on a server. This is where the CVS > files are kept and can be thought of like a database. On the other > end of the equation is your CVS client, whether that's the command- > line cvs tool in a Terminal window or BBEdit's CVS support. You use > this to manage what's called a "working copy." The working copy is a > checked-out copy of the files from the repository at a given point. > This can be a revision (e.g. 1.5.1 or 2.7) or a point in time (e.g. > 2006-03-02 21:33:00 or "yesterday"), or the latest bleeding edge of > what you're currently developing on, called HEAD in CVS lingo. > BBEdit works with files in working copies, and its CVS features don't > spring to life until you're using one. > > CVS workflow also goes in a "checkout, edit, commit" cycle, where you > get the files from the repository using either the "cvs checkout" > command to get a new working copy or the "cvs update" command to > update an existing one, make any changes you need, and then commit or > save the changes you made back to the repository. Anyone else who > had a working copy of the repository checked-out for their own use > could then do an update and would have your versions of the files. > There's a whole lot of "black magic" that takes place on the > repository side of things, and that's all covered in the CVS Book, > but you don't really need to worry about it for now. > > On Mar 2, 2006, at 9:13 PM, Allen Watson wrote: > >> I still don't get it. In BBEdit, setting up a "repository" seems to >> allow >> only for browsing to a local folder on my Mac. Is there some way >> for me to >> use BBEdit to co-edit source on a remote site? That's what I need. >> Working >> alone, I often use BBEdit's FTP browser to access my site, download >> several >> files, edit, preview, and then save to FTP again when I am done. I use >> another program (Interarchy) to mirror the site on my local hard >> drive, and >> it will download copies of everything I've modified. Now that a second >> person will also be editing files on the site, I'd like to be able >> to use >> BBEdit to access those files but somehow using CVS to play traffic cop >> between me and my co-worker in Vegas. I THOUGHT that was what the >> CVS menu >> in BBEdit was for, but apparently not. > > Instead of using FTP to copy files over, edit them, and then upload > them, you would use CVS to check out an initial working copy, make > your changes, and the commit them. BBEdit can handle the second and > third parts of that equation (and maybe the first, but I don't know > since I always use the command line "cvs checkout"). > >> She has suggested I look into obtaining a CVS client program, use >> that to >> download what I need, and then switch to BBEdit for the editing. Is >> that my >> best approach? > > I would install the developer tools from http://connect.apple.com > (free registration required). This will give you the command-line > cvs tool to use for checking out working copies, and then you can use > BBEdit to edit your files and commit your changes. The CVS Book's > tour section should be enough to get you going, along with your > coworker's and our help. :) > > I hope that clears things up a bit, and if you need any further > clarification don't hesitate to let us know. I've had nothing but > great results working with BBEdit and CVS (and Subversion) > repositories, and it is easier to deal with than the command-line > tool for most operations. > > Thanks, > Jeff -- <[EMAIL PROTECTED]> Scripts for OE and Entourage: <http://homepage.mac.com/allen_a_watson/AppleScripts_For_You> Entourage questions: <http://www.entourage.mvps.org/> -- ------------------------------------------------------------------ Have a feature request? Not sure the software's working correctly? If so, please send mail to <[EMAIL PROTECTED]>, not to the list. List FAQ: <http://www.barebones.com/support/lists/bbedit_talk.shtml> List archives: <http://www.listsearch.com/BBEditTalk.lasso> To unsubscribe, send mail to: <[EMAIL PROTECTED]>
