one would be willing
> to offer their thoughts.
>
> I'm using a single repository to hold multiple projects. Each of these
> projects uses third party code from a particular vendor. They may use
> different versions of that code, but this is handled well using vendor
> branches a
willing
> to offer their thoughts.
>
> I'm using a single repository to hold multiple projects. Each of these
> projects uses third party code from a particular vendor. They may use
> different versions of that code, but this is handled well using vendor
> branches as d
o hold multiple projects. Each of these
projects uses third party code from a particular vendor. They may use
different versions of that code, but this is handled well using vendor
branches as described in the SVN book, with a slight twist to
accomodate multiple projects.
- / (repository root)
On Thu, Mar 15, 2012 at 8:05 AM, Mark-E wrote:
>
> The section is setup like this in SVN:
>
> Archive/project1/trunk
> Archive/project2/trunk
> Archive/project3/trunk
>
> What I would like to be able to do is use svn co to check out the trunk
> folder for each project without specifically issuing
On Thu, Mar 15, 2012 at 05:40:23PM +0400, Konstantin Kolinko wrote:
> 1) do "svn co --depth immediates" for the repository root
> 2) and follow it by "svn up --set-depth" for the subfolders that you
> are interested in.
You can also use --depth empty in the first command to avoid having
all immedi
t regards,
>Konstantin Kolinko
Thanks for the tips Konstantin, I appreciate the help. I'll give it a try.
Regards,
Mark
--
View this message in context:
http://old.nabble.com/Question-on-checking-out-multiple-projects-tp33509611p33510088.html
Sent from the Subversion Users mailing list archive at Nabble.com.
2012/3/15 Mark-E :
>
> I am using OpenGrok as a search engine for SVN.
>
> I have an Archived section of obsolete code that users still want to be able
> to search.
> It is currently not searchable in our grok installation.
>
> The section is setup like this in SVN:
>
> Archive/project1/trunk
> Arc
not come across any
documentation that helps me understand if this is possible or not.
Does anyone know if this is possible using svn co and if so, what the proper
syntax is?
Regards,
Mark
--
View this message in context:
http://old.nabble.com/Question-on-checking-out-multiple-projects
Ryan, Thank you for straightening me out. I do want multiple projects in a
single repository, so I will start over using the first of your nice examples,
that is, with svn mkdir, etc.. Thank you for all your help. pcr
-Original Message-
From: Ryan Schmidt [mailto:subversion-20
s) you've chosen.
You'll have to decide whether you want multiple repositories, one for each
project, or a single repository containing multiple projects; there are
trade-offs either way. If you change your mind later, you can always change it
-- combine multiple repositories into one, or split a monolithic repository
into several smaller ones -- but again both operations come with consequences.
gt; given in appendix A of the subversion online book, which uses /var/svn/repos.
> (is it okay not to use /var?)
You can store the repository anywhere you like.
> How should this have been for multiple projects? Perhaps svn create
> /usr/svn/projectA/repos? Or svn create /usr/svn/repos/p
/repos. (is it
okay not to use /var?) How should this have been for multiple projects? Perhaps
svn create /usr/svn/projectA/repos? Or svn create /usr/svn/repos/projectA or
should the project directory be under trunk? Do you see my problem? Thanks for
your help.
Thanks for simple option 1, it could solve our problem.
Option 2 doesn't fit, cause of needing to do bunch of "svn copy ..." to tag
all projects and then tag to BigProject with pinned externals.
Of course it could be done without tagging all projects, just pinning
externals to revision of trunk, bu
> 1. Yes you're right, but even though I've done committing and updating
> externals I got the same message "svn: 'BigProject-trunks\Project1' is not
> under version control".
>
> 2. The usual way to create a tag doesn't fit our need of tagging all
> projects within one revision.
>
> For better u
Hello,
1. Yes you're right, but even though I've done committing and updating
externals I got the same message "svn: 'BigProject-trunks\Project1' is not
under version control".
2. The usual way to create a tag doesn't fit our need of tagging all
projects within one revision.
For better understan
On May 28, 2010, at 10:18, Sergii Ostroverkhov wrote:
> CMD script for init test repository:
> svnadmin create BigProject
>
> echo [general] > BigProject\conf\svnserve.conf
> echo anon-access = write >> BigProject\conf\svnserve.conf
>
> svn mkdir -m Project1 svn://localhost/BigProject/Project1
>
Hello,
CMD script for init test repository:
svnadmin create BigProject
echo [general] > BigProject\conf\svnserve.conf
echo anon-access = write >> BigProject\conf\svnserve.conf
svn mkdir -m Project1 svn://localhost/BigProject/Project1
svn mkdir -m Project1 svn://localhost/BigProject/Project1/tag
Vikrama Sanjeeva wrote:
Hi all,
Suppose If I have project A and project B in a same repository then
project B's version will change every time project A has something
committed to it, even if no work is being done in project B ?
Please confirm my understanding.
The global repository revisi
On Sat, Apr 3, 2010 at 3:51 AM, Andy Levy wrote:
> On Fri, Apr 2, 2010 at 20:22, Vikrama Sanjeeva
> wrote:
> > Hi all,
> >
> > Suppose If I have project A and project B in a same repository then
> project
> > B's version will change every time project A has something committed to
> it,
> > even
On Fri, Apr 2, 2010 at 20:22, Vikrama Sanjeeva wrote:
> Hi all,
>
> Suppose If I have project A and project B in a same repository then project
> B's version will change every time project A has something committed to it,
> even if no work is being done in project B ?
Individual items do not have
Hi all,
Suppose If I have project A and project B in a same repository then project
B's version will change every time project A has something committed to it,
even if no work is being done in project B ?
Please confirm my understanding.
Bye,
Viki.
21 matches
Mail list logo
