|
From: Heiko K. <hei...@me...> - 2009-01-08 09:30:07
|
Hi Nick, thanks for reporting the problem. I think it would be most useful if you add your files and the problem to the sourceforge tracker https://sourceforge.net/tracker/?group_id=54817&atid=474943 (hope that link works). There is not a lot of continous development going on in javaxdelta, so I don't think somebody will jump at it immediately. You should try to reduce the scope or even find the bug. But if you don't manage, and when somebody is updating javaxdelta at a later stage, it might be good to have a critical case. Best wishes, Heiko > To introduce myself to the javaxdelta developers, my name is Nick > Crossley. > > I have just started to use javaxdelta, and I have found a pair of files > where the delta command produces a bad patch, and/or where the patch is > not correctly applied by gdiffpatcher. The end effect is that running > the patch succeeds, but produces a file that is not equal to the > original target. > > The files involved are about 7Mb. I have not yet identified if the > problem is in the delta or the patch parts, nor have I yet tried to cut > down the file size to a minimum necessary to reproduce the problem. > > Is there any interest is my providing the two files at this stage, or > not until/unless I can reduce the scope more? > > Nick. > > > -------------------------------------------------------------------- > mail2web LIVE Free email based on Microsoft® Exchange technology - > http://link.mail2web.com/LIVE > > > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > Javaxdelta-devel mailing list > Jav...@li... > https://lists.sourceforge.net/lists/listinfo/javaxdelta-devel |