Donovan Baarda
2006-02-21 12:07:02 UTC
G'day Dave,
Note we are using the sourceforge lists/trackers/CVS etc. I'd suggest
subscribing to at least librsync-devel if you are doing devel work.
Cc'ing this to the devel list...
and give him CVS access if he wants, but it's probably a good idea to
post this stuff initially as a patch so we can go over it before
committing it.
I did have plans to switch to using libmd, openssl, or our own md4sum
implementation, selectable/detactable at configure time. The first step
would be to switch to the libmd/openssl API, which it sounds like your
guy has done...
time yet. Someone submitting patches will help encourage me to do stuff.
I just looked at the TODO in CVS and it really needs a clean... ideally
it would be a clear indication of future work. At the moment it's a mess
of old/new/speculative stuff. I'll clean it up soon...
Hmmm... there is a few outstanding bugs and patches too... I'll try to
tackle them this week.
Note we are using the sourceforge lists/trackers/CVS etc. I'd suggest
subscribing to at least librsync-devel if you are doing devel work.
Cc'ing this to the devel list...
Hi Donovan,
we have a guy working for the dole over here (under the community code
project - http://www.communitycode.org (site might be down atm).
Anyway, he has being trying to slowly fix the librsync files over 4GB
http://lists.gnu.org/archive/html/rdiff-backup-users/2006-02/msg00015.html
Excellent!!!we have a guy working for the dole over here (under the community code
project - http://www.communitycode.org (site might be down atm).
Anyway, he has being trying to slowly fix the librsync files over 4GB
http://lists.gnu.org/archive/html/rdiff-backup-users/2006-02/msg00015.html
Anyway, he seems to be finished - I think he used some MD4 bits from the
openssl libraries, and I have told him to post them to librsync-devel.
I hope you haven't gone off and solved it all already, and of course I
would appreciate a once over of his code if you have time.
It might be few days before its ready for a diff/patch submission yet.
Its seems to work....
Get him to post the patch up on SF. I can also add him as a developeropenssl libraries, and I have told him to post them to librsync-devel.
I hope you haven't gone off and solved it all already, and of course I
would appreciate a once over of his code if you have time.
It might be few days before its ready for a diff/patch submission yet.
Its seems to work....
and give him CVS access if he wants, but it's probably a good idea to
post this stuff initially as a patch so we can go over it before
committing it.
I did have plans to switch to using libmd, openssl, or our own md4sum
implementation, selectable/detactable at configure time. The first step
would be to switch to the libmd/openssl API, which it sounds like your
guy has done...
Anyway, just a heads up, let me know if you are doing any other work on
librsync, just so we can coordinate efforts
I'm still watching it, and have plans to do stuff, just haven't foundlibrsync, just so we can coordinate efforts
time yet. Someone submitting patches will help encourage me to do stuff.
I just looked at the TODO in CVS and it really needs a clean... ideally
it would be a clear indication of future work. At the moment it's a mess
of old/new/speculative stuff. I'll clean it up soon...
Hmmm... there is a few outstanding bugs and patches too... I'll try to
tackle them this week.
--
Donovan Baarda <***@minkirri.apana.org.au>
http://minkirri.apana.org.au/~abo/
Donovan Baarda <***@minkirri.apana.org.au>
http://minkirri.apana.org.au/~abo/