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

[PATCH] Issue 2213 - setting a max mail size

From: Jon Bendtsen <jbendtsen_at_laerdal.dk>
Date: Fri, 16 Jan 2009 15:20:54 +0100

Hi

The attached PATCH is one way of solving issue 2213
        http://subversion.tigris.org/issues/show_bug.cgi?id=2213
The method used in this PATCH is just a cut off once the sum
of diffs are larger than the limit. This means that log messages
and which files are changed, modified, changed, moved, ... are
not included in the count. If that is a problem, set a smaller limit.
Naturally the configration file accepts a default limit and
individual limits per group.

The PATCH is made against the latest? mailer.py from trunk,
revision 35280

Starting with revision 35280, this patch will cause complications
with some of the other patches that i will be sending shortly.

Applies fine:
        sameimportfix.txt

Fuzzy helps:
        binary_file_endings.txt

Problems and errors:
        header_detail.txt
        max_number_of_diffs.txt
        max_diff_size.txt

My intention is that all the functionality in the patches should be
available, so i am willing to do some work to get them all to apply
cleanly or with fuzzy. I just dont know the order which to do it in,
and i figured that once big patch that gave all the functionality
would not be well liked.

6 patches will arrive

JonB

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1028678

Hi

The attached PATCH is one way of solving issue 2213
        http://subversion.tigris.org/issues/show_bug.cgi?id=2213
The method used in this PATCH is just a cut off once the sum
of diffs are larger than the limit. This means that log messages
and which files are changed, modified, changed, moved, ... are
not included in the count. If that is a problem, set a smaller limit.
Naturally the configration file accepts a default limit and
individual limits per group.

The PATCH is made against the latest? mailer.py from trunk,
revision 35280

Starting with revision 35280, this patch will cause complications
with some of the other patches that i will be sending shortly.

Applies fine:
        sameimportfix.txt

Fuzzy helps:
        binary_file_endings.txt

Problems and errors:
        header_detail.txt
        max_number_of_diffs.txt
        max_diff_size.txt

My intention is that all the functionality in the patches should be
available, so i am willing to do some work to get them all to apply
cleanly or with fuzzy. I just dont know the order which to do it in,
and i figured that once big patch that gave all the functionality
would not be well liked.

6 patches will arrive

JonB

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1028678

Received on 2009-01-16 15:32:27 CET

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