[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] How to preserve file permissions when using svn commit

From: Mark Phippard <markphip_at_gmail.com>
Date: Fri, 2 May 2008 20:55:33 -0400

I believe permisssions on checkout are set by normal filesystem rules.

On May 2, 2008, at 8:52 PM, shertay <shertay_at_gmail.com> wrote:

>
> So is there any way to change the default permissions? Since I want
> other
> developers to be able to have w permissions too when they
> update,revert or
> any other actions performed..
>
>
>
> Steven Schwartz-2 wrote:
>>
>> Subversion should not attempt to "maintain" file permissions. The
>> repository holds artifacts (code) that can be checked out in a
>> variety
>> of contexts: development / sandbox, testing, deployment. Different
>> file
>> permissions are appropriate in each context. A reasonable default
>> is to
>> make newly-checked-out code rw for the owner, and read or null for
>> group
>> and other.
>>
>> Another perspective: the owner (and Unix group) -identities- will
>> probably differ in each of these contexts. You cannot assume that
>> the
>> effective permissions in one context should be the same.
>>
>> --Steve
>>
>>
>> -----Original Message-----
>> From: Mark Phippard [mailto:markphip_at_gmail.com]
>> Sent: Friday, May 02, 2008 10:37 AM
>> To: users_at_subclipse.tigris.org
>> Subject: Re: [Subclipse-users] How to preserve file permissions when
>> using svn commit
>>
>> On Thu, May 1, 2008 at 9:58 PM, shertay <shertay_at_gmail.com> wrote:
>>
>>> I realised that the file permission of files that I commited to
>>> the
>>> repository using command line "svn commit" changed. Initially they
>> are
>>> rw-rw-r, but the commited files in repository are rw-r-r only. May I
>> know is
>>> that a way to preserve the file permissions? or to configure the
>>> file
>>> permissions for svn commit??
>>
>> The is is really a Subversion question, not Subclipse. To answer it
>> though, Subversion does not manage, version, or store file
>> permissions. The lone exception is that on Unix systems you can
>> set a
>> property named svn:executable on a file, and if that file is set,
>> then
>> the client will set the executable bit on the file.
>>
>> --
>> Thanks
>>
>> Mark Phippard
>> http://markphip.blogspot.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
>> For additional commands, e-mail: users-help_at_subclipse.tigris.org
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
>> For additional commands, e-mail: users-help_at_subclipse.tigris.org
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/How-to-preserve-file-permissions-when-using-svn-commit-tp16996462p17030352.html
> Sent from the subclipse - users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
> For additional commands, e-mail: users-help_at_subclipse.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-05-03 02:57:16 CEST

This is an archived mail posted to the Subclipse Users mailing list.