"Ph. Marek" <email@example.com> writes:
>> Please provide a short description of the behaviour you intend to
>> implement. Some questions:
>> - Is there a way to enable/disable the behaviour?
> The whole thing is currently triggered by auto-props and the config option
Auto-props are just a way of avoiding the need to run "svn propset".
> "use-commit-times". If eg. a property "svn:owner" is set on a file, it will
> be sent to the repository as the current value.
> So you'd have in your ~/.subversion/config something like this:
> * = svn:text-time=yes;svn:owner=yes;svn:group=yes;svn:unix-mode=yes
> or whatever values you'd like, and they'd be set on commit (and import).
So the presence of svn:group say is not enough, I also need to have
use-commit-times set? That makes it different to svn:executable. I
don't like the overload of use-commit-times either.
How does svn:unix-mode interact with svn:executable?
How does svn:unix-mode interact with umask?
>> - If I change the owner/group/mode of the working copy does this get
>> committed, or do I have to do an explicit propset?
> On every commit because of text-changes the properties are set to the current
> values. Currently this happens *only* on text-changes, but read below.
I don't understand the your answer.
If I have the unix-mode stuff enabled is a "chmod" sufficient to cause
commit to store the new permissions or do I need to do an explicit
What happens if I "svn propset" one value and chmod a different value,
does one of the values get committed or is a conflict detected?
>> - I assume the owner/group/mode of the working copy files get set
>> during checkout, does it apply to directories as well?
> As I work with auto-properties, and these (currently) work only with files.
> But I thought about implementing auto-dir-props too.
Auto-props are just a way of avoiding "svn propset". What happens if
I "svn propset" one of your new properties on a directory?
>> - Non-root Unix users cannot usually change ownership, does this cause
>> lots of warnings or errors?
> No, this is silently ignored.
>> - Do updates modify the working copy owner/group/mode?
> I believe it does; but I'm not sure. I can't test at the moment.
>> - If an update changes the owner/group/mode does it generate conflicts
>> with local changes, or do conflicts only occur if the wc properties
>> are modified?
> The conflict handling is currently unspecified.
> But if these properties are handled like "svn:eol-style" (and cause a
> re-translation of the file), the new values would be in effect immediately.
So if I do a chmod to have local modifications is "svn update" simply
going to overwrite my changes?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Feb 8 19:29:32 2005