For my file-sync tech, I want to flip readonly bits within the filesystem
when I Curl-GET resources down from Svn. While mod_authz_svn adjudicates on
where a) resources are readable by the user in question and b) whether
writable.
If an item were readable, but not writable, the only way the end-us
So maybe the header added to HTTP GETs of resources would be:
resource-is-not-modifiable-by-you: true
*In the absence of this new feature of Subversion*
I'm going to have to encode something verbose in the repo itself as hidden
files:
/.sync/server-settings/users//readonly-masks.txt
An
Hello,
What is the story? How is this going to help Subversion users?
The idea sounds interesting. However, I'm not sure how it will help
the users. I don't mind whether I have Read Only or Read / Write
access to an FTP resource or another kind of remote data. I just know
whether I have access to
>
>
> What is the story? How is this going to help Subversion users?
>
> The idea sounds interesting. However, I'm not sure how it will help
> the users. I don't mind whether I have Read Only or Read / Write
> access to an FTP resource or another kind of remote data. I just know
> whether I have ac
On 21.07.2017 11:00, Paul Hammant wrote:
>
>
> What is the story? How is this going to help Subversion users?
>
> The idea sounds interesting. However, I'm not sure how it will help
> the users. I don't mind whether I have Read Only or Read / Write
> access to an FTP resource or ano
Paul Hammant wrote:> It will help the owners of subversion repos
preventing files from being> overwritten that they do not want to be
overwritten. [...]
>
> It will help subversion end-users not upset the owners of repositories
> by changing files (and committing them back) that there are not
suppo
May I go ahead and raise the feature request in Jira now?
I believe the approved process was discuss on mail-list, then raise in Jira.
- Paul
On Fri, Jul 21, 2017 at 5:40 AM, Julian Foad wrote:
> Paul Hammant wrote:> It will help the owners of subversion repos
> preventing files from being> ov
Paul Hammant wrote:
> May I go ahead and raise the feature request in Jira now?
Thanks for discussing here so far. Yes you may file it.
In order for it to progress to acceptance you probably also need to
clarify and finish discussing. It sounds like you have a clear idea of
what you want but it's
You are 100% correct.
For an anon svn-co (if allowed by the server), the default behavior should
be as is now - making working copy that is editable.
For an anon svn-co (if allowed by the server), the behavior if a new option
is specified - make the files readonly (Win and Unix derivatives)
For a
OK, I've added https://issues.apache.org/jira/browse/SVN-4691
I've tried to focus on the meat of the ask, and cover previous questions.
Also I've covered previous suggestions, though while welcome, would not
solve the same problem.
10 matches
Mail list logo
