On Thu, Apr 10, 2008 at 10:25 AM, <kmradke_at_rockwellcollins.com> wrote:
> Blair Zajac <blair_at_orcaware.com> wrote on 04/09/2008 10:39:46 PM:
>
> > Rares Vernica wrote:
> > > Hello,
> > >
> > > Is there a way to set the maximum file size for commits? That is, if I
>
> > > set the maximum file size to 4Mb and a user tries to commit a file
> which
> > > has 4.1Mb, the commit will fail.
> > >
> > > Thanks,
> > > Ray
> >
> > You can check this in a pre-commit script. You'll need to get a list of
> all
> > added or modified files using svnlook and then cat each one.
>
> Any other way? This seems a bit late in the game, and fairly inefficient.
> For
> example, we have a number of groups who have committed multiple DVD .iso
> files
> in one transaction.
>
> While I don't mind punishing them by making them wait to transfer 4G+ and
> then
> wait some more while the server cats the file to count the bytes, both of
> those actions are needlessly resource wasteful...
>
> I was hoping someone had experimented with some Apache options to limit
> transaction size. (Yet another thing on my todo list that I hope someone
> else has more experience with...) Possibly something like
> LimitRequestBody 4194304 ????
In that scenario, consider that Subversion only transfers differences
across the wire. So how would you handle a situation where a user
commits at 2MB file, then appends 3MB to it and commits that? Their
individual commits were both under 4MB, but the resulting file is now
5MB.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-04-10 16:51:20 CEST