[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Thanks

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: 2006-08-21 23:35:07 CEST

On Mon, 2006-08-21 at 13:45 -0700, The Dan Keefer wrote:

> Yes, I am largely unfamiliar with source code management and version
> control software. I understand most of the issues, but I know that the
> powers to be aren't going to want (or be able) to completely change
> everything we do.
> Every developer has his own copy of CF, SQL Server, and code.
> Typically when we are asked to either develop or or fix something, we
> do it on our local copy. Each of us copies our changed/new files onto
> a development server and copies the changed code of others onto our
> local copies. We are to check the time stamp of each file as it it
> copied.
> We are well aware of the problems with this process, which is why we
> are looking into Subversion.
> However, not only do our copies need to run independently of the
> server, but the server is used for testing development by
> non-programmers so it is considered the latest development copy,
> though there are works in progress.
> It SOUNDS like each time a file is changed, it goes into a new folder
> (potentially) so that the latest version isn't in the web site path
> anymore.

It is. When you commit, the version number changes so that if you
want, you are able to retrieve any version ever committed. However
the normal thing is to check out or update to the HEAD version - i.e.
the most recent anyone has committed. You can create branches for
work that should be isolated but again an update of a checked
out branch will pull the latest things committed to that branch.

  Les Mikesell
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 21 23:37:52 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.