[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Limit The size of Commit in SVN

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Tue, 4 Feb 2014 22:45:59 -0500

On Tue, Feb 4, 2014 at 7:25 AM, Stephen Connolly
<stephen.alan.connolly_at_gmail.com> wrote:
> Nope I cannot. I don't use windows, and I only use SVN for those projects I
> work on that are still on SVN.
>
> I think you are missing the point that *everyone* has been trying to get you
> to see...
>
> What is the benefit in stopping 1GB+ commits?

In my experience, they're almost inevitably mistakes. They're often
accidental including bulky binary files, which then are incredibly
painful to "obliterate" from the repository because there is still no
"obliterate" option for inappropriately stored files in the repository
itself, and from the current code lines, there *never will be* such an
option. The dump/filter/reload echanism is extremely painful for
clearing such accidentally stored binaries.

The other common error is accidentally relocating large source trees,
where an "mv" command is accidentally relocating entire sets of
projects rather than merely branches.

I'm not saying this is easy to build into Subversion, the pre-commit
filter would have to summarize and asses the size of the entire
commit. I'm just saying there are reasonable reasons to want such a
filter.
Received on 2014-02-05 04:47:19 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.