Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 13 Jul 2016 20:13:20 +0000
From: Greg Stein <gstein@gmail.com>
To: users@subversion.apache.org
Subject: Re: Commit Size Restriction
Message-ID: <20160713201320.GA58450@gmail.com>
References: <778fa859-63af-4329-912c-0e655807834b@googlegroups.com>
 <57869372.45d11c0a.aefa0.b3ea@mx.google.com>
 <578693ed.0890c20a.b7211.ffffe14b@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=unknown-8bit
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <578693ed.0890c20a.b7211.ffffe14b@mx.google.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
archived-at: Wed, 13 Jul 2016 20:13:23 -0000

The simplest mechanism to avoid large (new) files from getting
committed into your repository is to use the "LimitRequestBody"
directive in your Apache configuration. This is the mechanism that
we use on svn.apache.org

Cheers,
-g

On Wed, Jul 13, 2016 at 09:18:05PM +0200, bert@qqmail.nl wrote:
> How do you define ‘commit size’?
> With delta compression, re-use on copies of files and directory trees, etc. it is very hard to define what size a commit would be.
> 
> And as we have pluggable filesystem backends we don’t know what amount of disk space would be used after a commit.
> 
> 
> Personally I would just use a simple commit filter if necessary, to avoid users accidentally committing DVD images.
> 
> Bert
> 
> 
> Sent from Mail for Windows 10
> 
> From: Siva
> Sent: woensdag 13 juli 2016 16:07
> To: subversion-users
> Subject: Commit Size Restriction
> 
> Hi All,
> 
> My Subversion Edge is installed in Windows Server.
> 
> Is it possible to restrict commit size by repository or whole server?
> 
> Regards,
> Sivaram
> 
>