On Version Control again...

From: Alan Garny (someone_at_somewhere.com)
Date: 05/29/04 

Date: Sat, 29 May 2004 11:22:53 +0100

There have been a couple of threads on version control solutions lately. I
must confess that working on a one-person project, I thought that using a
version control system would be more of a pain in the neck than anything
else. I have therefore been using the very simple manual solution for ages.
Ie, I back up the whole structure of my project once in a while. Such a
solution has helped me in a few occasions, but the biggest drawback is that
its efficiency, obviously, relies on how often I back things up.

Anyway, since it had been years since I had last used a version control
system, I thought I would look around at what is available nowadays in the
hope that I could find a solution that would less tedious to use than what I
was used to.

Being in academia, I (obviously?) wanted an open source solution... :) After
reading several posts and assessing the situation as much as I could, I
decided to go for TortoiseSVN. I downloaded it and started to read the doc.
After an hour or so, I started to set things up for my project and another
non-computing related project.

Well, let me tell you this: once you know the basics of TortoiseSVN, it's
dead easy to get a project of yours under version control! So far, I really
like it and most importantly for me, I don't have lock/unlock files, etc.
something that I was very much dreading (from past experience). No, all I
need to do in the end is, after having exporting the whole project, is to
work as I usually did and then, once in a while, commit the root of my
project and TortoiseSVN takes care of everything. Very simple, really!

All that blurb to say that I am grateful to the Borland community for having
indirectly managed to convince me to have another look at version control
solutions. It had crossed my mind several times, but I had wrongly assumed
that nothing would have changed and that, therefore, it wasn't worth the
effort and time to look into what is now available. How wrong!

Ok, enough said! I am now a happy bunny with TortoiseSVN and I look forward
to working a lot on my project and still be able to retrieve *any* previous
of my project, should I need to. Just awesome! :)

    Alan.

Relevant Pages

  • Re: Looking for a good Python environment
    ... via TortoiseSVN or ... Eclipse, which can be hog. ... is for the source control plug-ins. ...
    (comp.lang.python)
  • Re: Version Control Sofwtare
    ... I am the only developer in my company and for vesrion control I just ... > actually using Version control Software? ... I needed a version control software. ... around too and decided for Subversion using TortoiseSVN ...
    (borland.public.delphi.non-technical)
  • Re: Source version control for Delphi 7
    ... > It was a combination of Subversion and the Tortoise client. ... > explorer is not the place to control what gets checked in and out, ... IMHO things don't get better than TortoiseSVN, ... > server what the hell is happening to the repository at any time ...
    (borland.public.delphi.non-technical)
  • Re: Quiet Airliners of the Future?
    ... >at least 25 minutes of electricity. ... would seem safe in guarding against 'Complete electrical failure', ... How many circuit breakers are involved in the Airbus flight control ... control system back into operation, ...
    (rec.aviation.piloting)
  • Re: [OT?] Simple AND/OR Simplistic single user ~CVS
    ... Any pointers to introduction to version control in general. ... a version control system by itself couldn't have prevented this. ... It's a way of keeping track of older revisions in your code base. ... In a group environment, step 6 would be "hand it over to the build & test group", then _they_ would build the 'real' version for shipment, test it, possibly make you go back and fix bugs, etc. ...
    (comp.dsp)