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,
Since you wanted to restrict access to 'documents' directory, you can
have access rules like,
> 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
> Amit kumar
> -----Original Message-----
> From: Les Mikesell [mailto:lesmikesell_at_gmail.com]
> Sent: Wednesday, May 08, 2013 7:22 PM
> To: Amit Kumar [IN7537]
> Cc: users_at_subversion.apache.org; amitsinghrana1_at_gmail.com
> Subject: Re: svn issue
> On Wed, May 8, 2013 at 2:25 AM, Amit Kumar [IN7537]<Amit_Kumar_at_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
Received on 2013-05-09 08:46:14 CEST