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

RE: RE: Re: Potential New User questions

From: Mark Shead <sheadm_at_optimalinternet.com>
Date: 2005-11-14 22:57:29 CET

It seems strange that your developers would regularly delete their
entire workspace in order to check out files once at a time. I don't
see how they could test any of their changes on their local machines
before doing a commit if they only had one file at a time. Even if
someone is working with .html they are usually going to need the images
folder to be able to see their changes.

One of the reasons that you can't get an individual file (I'm assuming)
is because subversion keeps all the local information about versioning
in .svn in the top level checked out directory. If a user pulls down a
file to just a random directory, the .svn directory is going to possibly
conflict with the .svn directories for other files that have been
individually checked out like that. By dealing with everything on the
directory level, subversion can check to make sure it isn't writing over
another working copy. There are other ways to do this of course, but
using a .svn directory seems to be a very good method that will work on
any operating system.

You *can* get individual files by doing something like this:
svn cat https://svn.something.com/trunk/file.txt > file.txt

However they are no longer under version control.

You also can check back in individual files by doing:
svn commit filename.txt

But they have to be in a working copy for this to work.

Generally if you are dealing with text documents, there isn't much
overhead in downloading a directory instead of just one file. Don't
forget that you can use -N to tell the checkout to just checkout files
and not subdirectories.

If checking out an entire directory seems to inconvenient, you might
give it a try and see if it really takes any more time than what you are
doing now. For example:

svn co http://server/repo/dir
cd dir
vim file.txt
svn commit -m "fixed every bug"

Is two less keystrokes than what you're wanting:

svn co http://sever/repo/dir/file.txt
vim file.txt
svn commit -m "fixed every bug"

If you are trying to checkout files over your cellphone connection or
something like that, the individual file checkout will be faster, but
for most use their isn't much of a speed difference unless you are
dealing with large binary files.

--Mark

-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2005@ryandesign.com]
Sent: Sunday, November 13, 2005 8:59 AM
To: Theisen, Gary
Cc: List Subversion
Subject: Re: Potential New User questions

On Nov 12, 2005, at 00:12, Theisen, Gary wrote:

> And that is primarily what our team would be using Subversion for.
> 'Just' version control, check in check out control, lock file if
> checked out etc. Often times, we are dealing with just 1 .asp or 1
> .html page and don't need to reversion or check out the entire
> directory that that
> 1 file lives in. I'd like to see the option in Subversion, to just
> check out and check in and reversion 1 file (or 2 files, etc) instead
> of said mentioned entire directory.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 14 23:01:29 2005

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