On 1/1/11 8:29 PM, Nico Kadel-Garcia wrote:
On Thu, Dec 30, 2010 at 9:29 AM, Stefan Sperling wrote:
What if the user later decides to use svnserve instead of apache?
How would the principle of least astonishment be applied then?
Do we tell those users to copy svnserve.conf from another reposi
On 12/30/10 7:41 AM, Bob Archer wrote:
I can also argue with the Principle of least astonishment:
So say we've added a new svnadmin option --dont-create-svnserve-
config,
and we've made svnserve skip repositories which don't have an
svnserve.conf file within them (putting aside the still unsolve
On 12/30/10 7:29 AM, Stefan Sperling wrote:
On Wed, Dec 29, 2010 at 09:03:16AM -0800, Philip Prindeville wrote:
On 12/29/10 8:34 AM, Nico Kadel-Garcia wrote:
On Wed, Dec 29, 2010 at 11:01 AM, Stefan Sperling wrote:
The initial concern raised in this thread was that there might exist
a hypoth
On Thu, Dec 30, 2010 at 9:41 AM, Bob Archer wrote:
> Is there really that much overhead in deleting the binary and insuring the
> correct permissions are used on the repository folders to "keep the honest,
> honest?" After all, any one with root/administrator access is able to bypass
> anythin
On Thu, Dec 30, 2010 at 9:29 AM, Stefan Sperling wrote:
> What if the user later decides to use svnserve instead of apache?
> How would the principle of least astonishment be applied then?
>
> Do we tell those users to copy svnserve.conf from another repository?
> Do we add a new option --create-
From: benjamin.ort...@wellsfargo.com
[mailto:benjamin.ort...@wellsfargo.com]
Sent: 01 January 2011 17:13
To: users@subversion.apache.org
Subject: On commit attempt, Server sent unexpected return value (403
Forbidden) in response to CHECKOUT
I'm trying to
I'm trying to integrate a SVN Authz authorization file with apache
configuration files to provide a solution for not just directory level
restrictions, but also file level restrictions. It's my understanding that the
SVN Authorization file is not capable of handling file-specific restrictions,
René Hjortskov Nielsen wrote on Sat, Jan 01, 2011 at 09:51:57 +0100:
> I’ve cross compiled subversion 1.6.15 on my i686 to the target system armv4l
> (product ib-nas3221-b).
>
> Everything seems to work, I can work with my old repository which has been
> moved to the target system.
>
> However,
I’ve cross compiled subversion 1.6.15 on my i686 to the target system armv4l
(product ib-nas3221-b).
Everything seems to work, I can work with my old repository which has been
moved to the target system.
However, when I do a commit through svnserve running on the target I get the
commonly know
