All,
I am setting up a new repository and have a question on how to handle
“common” code. Common refers to code which is shared across the multiple
systems that we deploy.
In addition to the common code, we also have system-specfic software
(custom code).
Given the typical SVN layout, what’
I use the externals property for my common code.
http://www.visualsvn.com/support/svnbook/advanced/externals/
From: C M [mailto:cmanalys...@gmail.com]
Sent: Tuesday, January 08, 2013 11:43 AM
To: users@subversion.apache.org
Subject: Advice on handing commo
If you have multiple projects that may edit the shared code I would recommend
treating it as vendor code:
http://www.visualsvn.com/support/svnbook/advanced/vendorbr/
We do that with multiple in-house projects run by multiple departments and it
allows us to share changes via merging.
From: John
Hello.
I read the Subversion documentation (in
particular the "Peg and Operative Revisions"
section) for how to handle versioning of
directories with names that contain the "@"
symbol. But I am still confused by something.
I want to use the "import" command to import a
tree that includes subdi
I'm happy to announce the release of Apache Subversion 1.6.20.
Please choose the mirror closest to you by visiting:
http://subversion.apache.org/download/#supported-releases
The SHA1 checksums are:
215083e6fc367b46fa76be82841115a32f0a5766 subversion-1.6.20.tar.gz
6b2af448dbc20b36099d
On 01/08/2013 12:11 PM, Leonard Wayne wrote:
Hello.
I read the Subversion documentation (in
particular the "Peg and Operative Revisions"
section) for how to handle versioning of
directories with names that contain the "@"
symbol. But I am still confused by something.
I want to use the "import"
