Sounds good, and thanks for the additional info Madan!
-Gary
-----Original Message-----
From: Madan U Sreenivasan [mailto:madan@collab.net]
Sent: Saturday, November 12, 2005 8:58 AM
To: Theisen, Gary
Cc: List Subversion
Subject: RE: Re: Potential New User questions
On Sat, 2005-11-12 at 04:42, 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.
I hope you understand that one user checking out a directory does not
mean another user will not be able to checkout. subversion provides
simultaneous edits. The user doesnt need to lock the file to use
check-it-out/use-it.
hmm, having said that, the state of the working copy file needs to be
stored someplace relative to the actual checked-out-file. Since this is
anyways a cost incurred at a directory level, it would serve greater
purpose to check out the whole directory.
If the unnecessary files in the directory is huge and if you are
concerned about disk space, I totally understand. In that case, you
could create a branch that reflects a directory tree as needed by each
user and the user should check out that branch. merge with trunk as and
when needed
I know all these are workarounds for NOT providing file level access.
IIRC, there are some discussions to implement such/similar features...
just hang in there :)
Regards,
Madan.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 14 22:11:47 2005