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

RE: Subversion Beginner - General Overview - Multiple Users

From: Jake Robb <jakerobb_at_mac.com>
Date: 2006-09-06 21:54:54 CEST

Hi Bob,

 

.NET is no different than any other environment in this regard.

 

The first time you use the repository, yes, you check out the entire thing.
You will now have a "working copy" on your local machine, which mirrors the
contents of the repository at the time you performed the checkout.

 

When you make changes locally, the repository is not affected at all. When
you are satisfied that your changes are complete, you "commit" your changes.
The Subversion client running on your machine only sends your changes, not
the entire working copy, to the server. You can commit all or part of your
changes, on a per-file or per-directory basis.

 

When someone else has made changes, you "update" your working copy to
retrieve those changes from the repository. The Subversion server only
sends the changes since your last commit, not the entire working copy, to
your local machine. You can update all or part of your working copy, on a
per-file or per-directory basis.

 

As a general good practice, most of us do not commit the compiled binaries
to the repository - only the human-editable files. In accordance with this
practice, one should not expect to be able to check out a fresh working copy
and simply "run" the software whose source code is in the repository. To
get a runnable version of the latest code, you need to check out a working
copy and build it (using scripts, IDE, command line, whatever).

 

-Jake

 

 

  _____

From: Bob Butterworth [mailto:BButterworth@techpro.com]
Sent: Wednesday, September 06, 2006 3:02 PM
To: users@subversion.tigris.org
Subject: RE: Subversion Beginner - General Overview - Multiple Users

 

Great, I'll make sure I check out that ericsink.com site. I have read some
of the SVN Book.

 

I just don't get fully how it pertains to the .Net Environment

 

Can someone who does .net work explain kind of the timeline of it?

 

As it seems to me this is what you have to do. Let's say I have Project1 in
a repository.

 

To work on Project1 in .net, it seems to me I need to have all the project1
files on my computer.

 

So I check out all files in Project1 and it will copy it down to my
computer. If I have a version of project1 already on my computer, it will
update it and only copy down from the server what it needs to sync the too.

 

I then can make changes, compile, debug. .Net will change some files in the
/bin directory during a compile. When i'm done, I check back in and it will
update any files that have changed?

 

So from what I understand I have to Check Out All project files so I can
work on them, which one project could be a TON of files. But to compile it i
have to have those files.

 

You can see i'm a little confused.

 

But i'll check out the ericsink site to see if I can get a better grasp

 

Thanks for your help!

 

 

 

 From: Jeff Marder [mailto:jeff.marder@yahoo.com]
Sent: Wednesday, September 06, 2006 1:15 PM
To: Bob Butterworth
Subject: Re: Subversion Beginner - General Overview - Multiple Users

I think Eric Sink's source control HOWTO is a really great way to get
started. Although it is about source control in general and not specifically
Subversion the same concepts apply. The chapter on repositories is, in my
opinion, the clearest explanation of what a repository is and how it
functions.

http://www.ericsink.com/scm/source_control.html

Of course, if you haven't already taken a look at the Subversion book you'll
want to do that as well.

http://svnbook.red-bean.com/

Jeff

----- Original Message ----
From: Bob Butterworth <BButterworth@techpro.com>
To: users@subversion.tigris.org
Sent: Wednesday, September 6, 2006 1:33:14 PM
Subject: Subversion Beginner - General Overview - Multiple Users

Hi Everyone. I've been a programmer for a while now and I've recently needed
at an increasing rate version control on my projects. After some research
i've decided on Subversion. But I have a few general questions about the
whole thing.

 

Currently have I have a .net project on my local computer, and that is where
it stays. No one else can work on it but me, and occasionally I back it up.

 

If I set up a subversion server were multiple developers are accessing it
for their projects, including me, how exactly does this work?

 

If I have the whole project with code on the server, does it get copied down
to my local computer when I check it out. I can then work on it, and check
back in the whole project? Does it then copy back up any changed files?

 

Do I keep my local copy of the project or do I always download everything
from the server.

 

These may sound like stupid questions but i'm just trying to grasp how this
works. Thanks for all your help

 

Bob

 

Bob Butterworth

 

Director of Web Development

 <mailto:bbutterworth@techpro.com> bbutterworth@techpro.com

----------------------------------------------------------

 <http://www.techpro.com/>

Direct Line: 630 .938 .5306
Direct Fax: 630 .845 .4606
Toll Free: 800 .262 .0537 ext.106
318 Anderson Boulevard
Geneva, IL 60134

----------------------------------------------------------

 <http://www.techpro.com/> w w w . t e c h p r o . c o m

 

TechPro E-Mail Disclaimer

The information contained in this e-mail and any accompanying documents is
confidential, may be privileged, and is intended solely for the person
and/or entity to whom it is addressed (i.e. those identified in the "To" and
"Cc" box). They are the property of TechPro, Inc. Unauthorized review, use,
disclosure, or copying of this communication, or any part thereof, is
strictly prohibited and may be unlawful. If you have received this e-mail in
error, please return the e-mail and attachments to the sender and delete the
e-mail and attachments and any copy from your system. TechPro, Inc. Thank
you for your cooperation.

 

 
Received on Wed Sep 6 21:57:00 2006

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