For this patch, it seems that you want to just set the "binary" flag
at the appropriate point. The attached patch will throw out all of the
potential label information about the changed revision and timestamp.
If you want to keep the "Forced Binary" annotation in there, then
maybe append that to the label?
I'll also note that you can use change.path.endswith('.' + ending)
rather than the regular expression stuff.
Cheers,
-g
On Fri, Jan 16, 2009 at 15:21, Jon Bendtsen <jbendtsen_at_laerdal.dk> wrote:
> Hi
>
> The attached PATCH is a alternative way of solving issue 2213,
> but it is the nearest issue i can find.
> http://subversion.tigris.org/issues/show_bug.cgi?id=2213
> The method used in this PATCH is a list of file endings which are
> forced to be considered binary, even if they look like text to a diff.
> We needed this because we have some programs that creates
> some .prproj files which are video related and really big.
>
> Naturally the configration file accepts a default list and
> individual lists 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:
> header_detail.txt
>
>
> Problems and errors:
> max_number_of_diffs.txt
> max_mail_size.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=1028679
> Hi
>
> The attached PATCH is a alternative way of solving issue 2213,
> but it is the nearest issue i can find.
> http://subversion.tigris.org/issues/show_bug.cgi?id=2213
> The method used in this PATCH is a list of file endings which are
> forced to be considered binary, even if they look like text to a diff.
> We needed this because we have some programs that creates
> some .prproj files which are video related and really big.
>
> Naturally the configration file accepts a default list and
> individual lists 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:
> header_detail.txt
>
>
> Problems and errors:
> max_number_of_diffs.txt
> max_mail_size.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=1028679
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1041193
Received on 2009-01-21 14:39:35 CET