You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Amit Kumar [IN7537]" <Am...@mindtree.com> on 2013/05/08 09:25:57 UTC
svn issue
Hi,
I found an issue in SVN. Suppose there are 10 project is in directory. And I want to update only 9 project. There is no option to lock one project not to update.
By this issue I get problem. I will request you to solve this issue.
Thanks & Regards,
Amit kumar | Senior Software Engineer | P +91 80 670 60718 | M +91 9740012743 | www.mindtree.com<https://indiamail.mindtree.com/exchweb/bin/redir.asp?URL=http://www.mindtree.com/>
MindTree Limited | West Campus, Global Village, RVCE Post, Mysore Road, Bangalore, India - 560 059 | Welcome to possible
________________________________
http://www.mindtree.com/email/disclaimer.html
Re: svn issue
Posted by Prabhu Gnana Sundar <pr...@collab.net>.
On 05/09/2013 10:46 AM, Amit Kumar [IN7537] wrote:
> Hi les,
>
> Thanks for reply. But in my condition there are 77 items are in parent folder which is group of project and some other folder like image location, document location. All project folder is required except like documents and image folder.
> so I have to check out from parent folder only. Sometimes other team create new project. If I take full update then only all project will come in my local or all will update including new project.
Let us assume you have a file structure like,
/trunk
|
|- proj1
|
|- file1
|- file2
|- proj2
|- file3
|- file4
|- proj3
|
|
|- proj77
|- documents
|- images
Since you wanted to restrict access to 'documents' directory, you can
have access rules like,
[reponame:/trunk/documents]
user=
[reponame:/trunk/proj-created-by-other-team]
user=
[reponame:/trunk]
*=rw
> I want to lock some folder and then I want take full update and I want to update only project folder.
I don't understand the scenario you described.
You can restrict access to a folder by the above said method and also
grant full access by just "user=rw".
If you wanted to update only only project folder, you can do so by,
$ svn update project-folder
--prabhugs
>
>
> Regards,
>
> Amit kumar
>
>
>
>
> -----Original Message-----
> From: Les Mikesell [mailto:lesmikesell@gmail.com]
> Sent: Wednesday, May 08, 2013 7:22 PM
> To: Amit Kumar [IN7537]
> Cc: users@subversion.apache.org; amitsinghrana1@gmail.com
> Subject: Re: svn issue
>
> On Wed, May 8, 2013 at 2:25 AM, Amit Kumar [IN7537]<Am...@mindtree.com> wrote:
>> I found an issue in SVN. Suppose there are 10 project is in directory.
>> And I want to update only 9 project. There is no option to lock one
>> project not to update.
>>
>> By this issue I get problem. I will request you to solve this issue.
> Why is that a problem? You should be able to commit to any part you
> want unless access control blocks it. And normally you would only check out the project(s) that you are working on in the first place.
> Or are you talking about the revision numbers being global for the repository? That's just the way subversion works - and a feature.
>
> --
> Les Mikesell
> lesmikesell@gmail.com
>
> ________________________________
>
> http://www.mindtree.com/email/disclaimer.html
Re: svn issue
Posted by Ryan Schmidt <su...@ryandesign.com>.
On May 9, 2013, at 00:16, Amit Kumar wrote:
> Thanks for reply. But in my condition there are 77 items are in parent folder which is group of project and some other folder like image location, document location. All project folder is required except like documents and image folder.
> so I have to check out from parent folder only. Sometimes other team create new project. If I take full update then only all project will come in my local or all will update including new project.
> I want to lock some folder and then I want take full update and I want to update only project folder.
Well "lock" isn't the term for this concept in Subversion. What you're looking for is a "sparse" working copy.
Re: svn issue
Posted by Les Mikesell <le...@gmail.com>.
On Thu, May 9, 2013 at 12:16 AM, Amit Kumar [IN7537]
<Am...@mindtree.com> wrote:
>
> Thanks for reply. But in my condition there are 77 items are in parent folder which is group of project and some other folder like image location, document location. All project folder is required except like documents and image folder.
> so I have to check out from parent folder only. Sometimes other team create new project. If I take full update then only all project will come in my local or all will update including new project.
> I want to lock some folder and then I want take full update and I want to update only project folder.
I see others have described how to get a sparse working copy but
personally I'd rearrange the repository layout to match the structure
so you can check out one top level directory and get what you want.
If that is the way everyone uses the repository, perhaps you could
move the 77 things you want under a new upper-level directory parallel
to the one you don't want. Or, if everyone uses different parts,
group them under directories that match the use patterns, then add a
new directory that you check out containing svn externals that pull
the other components into the right places and others can do the same
for their own layouts. The bad (or good, depending on your use
patterns and tools...) side of externals is that commits don't
automatically recurse into the folders pulled through external
references. Checkouts and updates follow them automatically, but you
have to explicitly commit changes separately. Externals also make it
much easier to work with separate trunk/branches/tags folders at
project-level folders for various components with separately-managed
component releases, but it doesn't sound like you are using that
convention in your repository now.
--
Les Mikesell
lesmikesell@gmail.com
RE: svn issue
Posted by "Amit Kumar [IN7537]" <Am...@mindtree.com>.
Hi les,
Thanks for reply. But in my condition there are 77 items are in parent folder which is group of project and some other folder like image location, document location. All project folder is required except like documents and image folder.
so I have to check out from parent folder only. Sometimes other team create new project. If I take full update then only all project will come in my local or all will update including new project.
I want to lock some folder and then I want take full update and I want to update only project folder.
Regards,
Amit kumar
-----Original Message-----
From: Les Mikesell [mailto:lesmikesell@gmail.com]
Sent: Wednesday, May 08, 2013 7:22 PM
To: Amit Kumar [IN7537]
Cc: users@subversion.apache.org; amitsinghrana1@gmail.com
Subject: Re: svn issue
On Wed, May 8, 2013 at 2:25 AM, Amit Kumar [IN7537] <Am...@mindtree.com> wrote:
>
> I found an issue in SVN. Suppose there are 10 project is in directory.
> And I want to update only 9 project. There is no option to lock one
> project not to update.
>
> By this issue I get problem. I will request you to solve this issue.
Why is that a problem? You should be able to commit to any part you
want unless access control blocks it. And normally you would only check out the project(s) that you are working on in the first place.
Or are you talking about the revision numbers being global for the repository? That's just the way subversion works - and a feature.
--
Les Mikesell
lesmikesell@gmail.com
________________________________
http://www.mindtree.com/email/disclaimer.html
Re: svn issue
Posted by Les Mikesell <le...@gmail.com>.
On Wed, May 8, 2013 at 2:25 AM, Amit Kumar [IN7537]
<Am...@mindtree.com> wrote:
>
> I found an issue in SVN. Suppose there are 10 project is in directory. And I
> want to update only 9 project. There is no option to lock one project not to
> update.
>
> By this issue I get problem. I will request you to solve this issue.
Why is that a problem? You should be able to commit to any part you
want unless access control blocks it. And normally you would only
check out the project(s) that you are working on in the first place.
Or are you talking about the revision numbers being global for the
repository? That's just the way subversion works - and a feature.
--
Les Mikesell
lesmikesell@gmail.com
RE: svn issue
Posted by Andrew Reedick <An...@cbeyond.net>.
You can do a fresh checkout and not include project10 in the initial update:
svn co -N svn://.../top_dir
cd top_dir
cd svn update project1 project2 ... project 9
Future 'svn update' commands in the top_dir directory will only update projects 1 through 9.
Or you can explicitly not update project 10:
Windows CMD shell:
for /f %i in (' svn ls ^| findstr /v project10') do @svn update %i
ksh/bash:
svn ls | grep -v project 10 | xargs svn update
Disclaimer: Top posting because Outlook has crushed my spirit.
From: Amit Kumar [IN7537] [mailto:Amit_Kumar@mindtree.com]
Sent: Wednesday, May 08, 2013 3:26 AM
To: users@subversion.apache.org
Cc: amitsinghrana1@gmail.com
Subject: svn issue
Hi,
I found an issue in SVN. Suppose there are 10 project is in directory. And I want to update only 9 project. There is no option to lock one project not to update.
By this issue I get problem. I will request you to solve this issue.
Thanks & Regards,
Amit kumar | Senior Software Engineer | P +91 80 670 60718 | M +91 9740012743 | www.mindtree.com<https://indiamail.mindtree.com/exchweb/bin/redir.asp?URL=http://www.mindtree.com/>
MindTree Limited | West Campus, Global Village, RVCE Post, Mysore Road, Bangalore, India - 560 059 | Welcome to possible
________________________________
http://www.mindtree.com/email/disclaimer.html