[Xapian-tickets] [Xapian] #300: Test failure : apitest, bigoaddvalue

Xapian nobody at xapian.org
Wed Oct 29 17:55:02 GMT 2008


#300: Test failure : apitest, bigoaddvalue
-------------------------------+--------------------------------------------
 Reporter:  charliejuggler     |        Owner:  richard
     Type:  defect             |       Status:  closed 
 Priority:  normal             |    Milestone:  1.0.9  
Component:  Test Suite         |      Version:  1.0.8  
 Severity:  normal             |   Resolution:  fixed  
 Keywords:                     |    Blockedby:         
 Platform:  Microsoft Windows  |     Blocking:         
-------------------------------+--------------------------------------------

Comment(by olly):

 Thanks for looking in to this.

 TortoiseSVN is essentially to blame here - GNU patch doesn't behave that
 way (it just gives an informational message to say what offset it had to
 apply to get the patch to match), and that's the de facto standard patch
 applying tool.  One can't expect people to additionally test patches apply
 with patch programs on an OS they don't run.  And indeed a major reason
 for sending patches rather than the changed sources is that you can still
 apply them if the underlying code changes in areas not touched by the
 patch.  So not allowing an offset nullifies one big advantage of sending a
 patch.

 You can get a port of GNU patch here:

 http://gnuwin32.sourceforge.net/packages/patch.htm

-- 
Ticket URL: <http://trac.xapian.org/ticket/300#comment:15>
Xapian <http://xapian.org/>
Xapian



More information about the Xapian-tickets mailing list