You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by bruce <be...@earthlink.net> on 2004/08/25 00:59:52 UTC
continuing subversion/svnserve questions...
thanks....
in looking through google/the 'subversion docs' ,i'm still at a loss as to
how to actually accomplish what i want to do...
i want to setup a system where one group of users will identify functions
that need to be created. each function will have it's own dir/file. as the
users identify a function, i envision them also creating the repository
directory for the function, and the initial template for the function within
the directory.
another group of users will then be responsible for building the functions,
and modifying the files within the repository file/directories in the
repository structure.
i also envision users who will act as testers of the functions. once the
test person verifies that the file/function works, i'd like for the test
person to be able to copy the file/function into a 'valid' directory. the
'valid' directory would basically be a storage of the working/complete
functions/files.
my question has to do with how this kind of environment should be setup. is
it possible within 'subversion' to actually 'tag' a file, or set a property
that can be used to denote that the given version of the file is 'good'? or
would it be better to set up a directory were i would just copy the 'working
files' to once they were verified? would this be a 'branch'?
it seems as though i'm making this a little more complex than it has to
be... with msoft vss, i could simply creae the different dirs, and move/copy
the underlying files as i needed to.. so i'm fairly certain that what i'm
trying to do is pretty straight-forward if i really understood
subversion...!!!
also, in using the tortise client, and reviewing test files in a test
repository, it appears that revisions are integers... does subversion using
integers exclusively, or is it possible to use the dot '.' format for
version/revision numbers, or am i confusing the role/usage of
revision/version numbers with subversion..
thanks for all/any pointers/comments/etc...
-bruce
-----Original Message-----
From: Patrick Smears [mailto:patrick.smears@ensoft.co.uk]
Sent: Tuesday, August 24, 2004 3:10 PM
To: bruce
Cc: users@subversion.tigris.org
Subject: RE: accessing a single file from svnserve
These questions are probably more appropriate for the TortoiseSVN mailing
list, but see inline...
On Tue, 24 Aug 2004, bruce wrote:
> now, how can i get a single directory/file from the repository via
> either the command line, or from the tortise client?
You cannot get a single file, you always have to get a directory. You
specify the directory as part of the URL in the checkout.
> do i need to have prior knowledge of what the file/directory is called?
Yes, but there are ways to find that out (see below)
> i'm looking for a way to kind of be able to review the underlying
> dir/tree structure and then to be able to select the dir/file from the
> tree that i need to work on...
Right-click on the desktop and choose "Repo-browser" from the Tortoise
menu. This gives you a way to browse through the repository without
checking out a working copy...
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: file/dir checkout within subversion...
Posted by bruce <be...@earthlink.net>.
ok...
to make sure i understand. the only way to really get a single 'working
file' is to have one file per directory, which would allow me to simply
checkout the dir containing the single file... is this what you're saying
regarding how subversion works...
thanks...
-bruce
-----Original Message-----
From: Ulrich Eckhardt [mailto:eckhardt@satorlaser.com]
Sent: Wednesday, August 25, 2004 3:24 AM
To: users@subversion.tigris.org
Subject: Re: file/dir checkout within subversion...
bruce wrote:
> the docs/searching through google implies that you can only 'check-out' a
> directory, and that you cannot checkout an individual file. is this
> correct? if i've misunderstood, can someone provide insight into how can
> you check out a single file???
You can retrieve a single file via 'svn cat URL'.
In order to create a working copy(something you work on and commit changes
from), svn needs to store its metadata somewhere and that is in the .svn
subdir. That is why you can't create a working copy of a single file.
Uli
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: file/dir checkout within subversion...
Posted by Ulrich Eckhardt <ec...@satorlaser.com>.
bruce wrote:
> the docs/searching through google implies that you can only 'check-out' a
> directory, and that you cannot checkout an individual file. is this
> correct? if i've misunderstood, can someone provide insight into how can
> you check out a single file???
You can retrieve a single file via 'svn cat URL'.
In order to create a working copy(something you work on and commit changes
from), svn needs to store its metadata somewhere and that is in the .svn
subdir. That is why you can't create a working copy of a single file.
Uli
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
file/dir checkout within subversion...
Posted by bruce <be...@earthlink.net>.
also,
the docs/searching through google implies that you can only 'check-out' a
directory, and that you cannot checkout an individual file. is this correct?
if i've misunderstood, can someone provide insight into how can you check
out a single file???
thanks...
-bruce
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
'looking' at/displaying files in a tree
Posted by bruce <be...@earthlink.net>.
hi...
if i do a 'svn ls svn:\\....' i get the top of the tree. is there a
command/way to be able to display the underlying dirs/files of a tree as
well?
thanks
-bruce
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: continuing subversion/svnserve questions...
Posted by Joerg Hessdoerfer <Jo...@sea-gmbh.com>.
Hi,
On Wednesday 25 August 2004 02:59, bruce wrote:
> thanks....
[...]
>
> i also envision users who will act as testers of the functions. once the
> test person verifies that the file/function works, i'd like for the test
> person to be able to copy the file/function into a 'valid' directory. the
> 'valid' directory would basically be a storage of the working/complete
> functions/files.
>
> my question has to do with how this kind of environment should be setup. is
> it possible within 'subversion' to actually 'tag' a file, or set a property
> that can be used to denote that the given version of the file is 'good'? or
> would it be better to set up a directory were i would just copy the
> 'working files' to once they were verified? would this be a 'branch'?
>
If I understand you correctly, then, yes, your testers could just 'svn cp' the
'accepted' functions to a 'valid directory'. Now, if your coders modify those
functions, I assume they need re-testing, which would then take place in the
'original location'. After testing again, they would be copied again.
This would have the benefit of always having a working 'active' function tree.
This is something like tagging, and we use this style for our in-house
products, it fits our development model quite well.
The big advantage of such a scheme in your case is, that you can 'accept'
individual files as needed.
> it seems as though i'm making this a little more complex than it has to
> be... with msoft vss, i could simply creae the different dirs, and
> move/copy the underlying files as i needed to.. so i'm fairly certain that
> what i'm trying to do is pretty straight-forward if i really understood
> subversion...!!!
>
> also, in using the tortise client, and reviewing test files in a test
> repository, it appears that revisions are integers... does subversion using
> integers exclusively, or is it possible to use the dot '.' format for
> version/revision numbers, or am i confusing the role/usage of
> revision/version numbers with subversion..
>
> thanks for all/any pointers/comments/etc...
>
> -bruce
No, svn uses integers, period. This revision number is just a 'transaction
counter', and should not have anything to do with project version numbers.
(Except your release could point back to a svn revision, for reference).
HTH,
Jörg
--
Leading SW developer - S.E.A GmbH
Mail: joerg.hessdoerfer@sea-gmbh.com
WWW: http://www.sea-gmbh.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org