Re: [rdiff-backup-users] Restarting development

[Jakob Unterwurzacher]

Am 05/04/10 19:08, schrieb Josh Nisly:
> I propose that we, at least for now, pull the Unicode changes out of
> CVS. This is unfortunate for a number of reasons, but hopefully we can
> bring back in transition code that will make full support possible.
> Additionally, we need to develop a comprehensive test suite that runs on
> all supported platforms. Code changes should be accompanied by tests.
>
> Once the unicode changes are pulled back out, I've a fair number of
> patches sitting in my own queue that can go in.

@Josh Nisly:
Glad to hear that developement continues!

As i am not familiar with python, i could contribute command-line based 
function tests (on linux) - would that be helpful?

When should we start sending patches? :)



Am 05/04/10 20:25, schrieb Daniel Miller:
> I've been working on a new implementation of rdiff-backup since about a month 
> ago when I dug into the current codebase and discovered its disappointing 
> quality. While what I have right now is functional and works on simple cases, 
> it does not cover the broad range of features currently offered by 
> rdiff-backup. I could use some help in bringing it up to par if others are 
> interested in the path I have taken. While I have used the current codebase for 
> direction and inspiration, I have started with a clean slate for several 
> reasons:

@Daniel Miller:
I don't care about Windows or OS X, so i would be glad to try out your 
-ng version. What i care about is robustness on linux. I had 
rdiff-backup repositories blow up too many times in the face of an 
unstable network connection. That's probably easier to achieve with a 
smaller and cleaner codebase.
Is -ng command-line compatible?

@All:
I hope, however, that improvements in either version can be shared as 
much as possible. That would be easier if both versions used the same VCS.


Best regards
Jakob