I don't have deep experience with source control, and would
like to use TortoisSVN on a local host, ie. with no server.
Although I didn't like the fact that any change to the repository,
even when it involved a different project, increased the revision
number, I read in the documentation that it wasn't really not that big
a deal: Just write down that public release 1.0 maps to such and such
revision number in SVN, and that's it.
But... I just imported and commited a file that has a name that
already exists in another project in the repository... and SVN failed
because of this :-/
=> Do you confirm that having a single repository to host more than
one project means that filenames must be identical throughout all the
projects? IOW, you must set up one repository per project to avoid
filename clashing?
And if you know of a good, short, no-brainer guide to working with
SVN, I'm interested.
Hello I don't have deep experience with source control, and would like to use TortoisSVN on a local host, ie. with no server. Although I didn't like the fact that any change to the repository, even when it involved a different project, increased the revision number, I read in the documentation that it wasn't really not that big a deal: Just write down that public release 1.0 maps to such and such revision number in SVN, and that's it.
in fact revision numbers are very usefull in a long run ...
Quote:
But... I just imported and commited a file that has a name that already exists in another project in the repository... and SVN failed because of this :-/
i haven't noticed such problems with keeping several eclipse projects
in the same repository. Each project had standard eclipse/ant/etc
configuration files.
Quote:
"Error: File already exists: filesystem C:/Repository/db', transaction '10-1', path '/my_proj2/Project1.cfg' => Do you confirm that having a single repository to host more than one project means that filenames must be identical throughout all the projects? IOW, you must set up one repository per project to avoid filename clashing?
just create a separete folder for each project in the repository root.
Quote:
And if you know of a good, short, no-brainer guide to working with SVN, I'm interested.
On 12 Sep 2006 07:35:07 GMT, Marek TROFIMIUK <mt20863@sgh.waw.pl>
wrote:
Quote:
in fact revision numbers are very usefull in a long run ...
I'm sure they are. What I meant is that if you use a single repository
(which is the default, and I was told it was OK to host several
projects in one repo), the revision number will increase even when
someone commits stuff in a different project, ie. even if nothing
changed in the project you're working on.
Quote:
just create a separete folder for each project in the repository root.
That's what I think I did: When importing a project when
right-clicking on a folder in Windows Explorer:
file:///C:/Repository/my_new_project/
Isn't this a new folder? Do I need to do something else when adding a
new project?
On 12 Sep 2006 07:35:07 GMT, Marek TROFIMIUK <mt20863@sgh.waw.pl> wrote:
Quote:
in fact revision numbers are very usefull in a long run ...
I'm sure they are. What I meant is that if you use a single repository (which is the default, and I was told it was OK to host several projects in one repo), the revision number will increase even when someone commits stuff in a different project, ie. even if nothing changed in the project you're working on.
but it's doesn't change anything in other projects.
SVN server stores information about rev numbers for each file.
Quote:
Quote:
just create a separete folder for each project in the repository root.
That's what I think I did: When importing a project when right-clicking on a folder in Windows Explorer: file:///C:/Repository/my_new_project/ Isn't this a new folder? Do I need to do something else when adding a new project?
in repo browser you can create the folder structure before importing data
i think the book recommends folder structure with truck, branches and
tags directories. you can also browse the public repo of the apache
fundation at http://svn.apache.org/viewvc/.
On 12 Sep 2006 07:35:07 GMT, Marek TROFIMIUK <mt20863@sgh.waw.pl> wrote:
Quote:
in fact revision numbers are very usefull in a long run ...
I'm sure they are. What I meant is that if you use a single repository (which is the default, and I was told it was OK to host several projects in one repo), the revision number will increase even when someone commits stuff in a different project, ie. even if nothing changed in the project you're working on.
but it's doesn't change anything in other projects. SVN server stores information about rev numbers for each file.
Not so. Read the section on Revisions in the svnbook. Subversion
increments the repository revision for each checkin. The entire repo
has the same revision. So checking in a change to a file will
increment the repository's revision.
Note: A working copy may have mixed revisions and you can create
branches and tags from mixed revsions.
Quote:
Quote:
just create a separete folder for each project in the repository root.
That's what I think I did: When importing a project when right-clicking on a folder in Windows Explorer: file:///C:/Repository/my_new_project/ Isn't this a new folder? Do I need to do something else when adding a new project? in repo browser you can create the folder structure before importing data i think the book recommends folder structure with truck, branches and tags directories. you can also browse the public repo of the apache fundation at http://svn.apache.org/viewvc/.
The MyLounge.com forum is intended for informational use only and should not
be relied upon and is not a substitute for any advice. The information contained
on MyLounge.com are opinions and suggestions of members and is not a representation
of the opinions of MyLounge.com. MyLounge.com does not warrant or vouch for
the accuracy, completeness or usefulness of any postings or the qualifications
of any person responding. Please consult a expert or seek the services of an
attorney in your area for more accuracy on your specific situation. Please note
that our forums also serve as mirrors to Usenet newsgroups. Many posts you see
on our forums are made by newsgroup users who may not be members of MyLounge.com
Term of Service