Displaying 7 results from an estimated 7 matches for "perlundq".
Did you mean:
derlund
2016 Jan 07
2
LGPL relicense port of rsync
Hi,
I am maintaining a port of rsync (https://github.com/perlundq/yajsync)
which is GPL:ed of course. The main purpose of the project is to
provide a Java API library for the rsync protocol. It would
therefore be really nice to be able to use LGPL as the license.
But in order to do so I would first have to get a list of all the
individual contributors to rsync a...
2013 Oct 21
1
use_safe_inc_flist not set for 3.1.0 client -> 3.0.9 daemon
Hi,
When using the latest rsync 3.1.0 client, connecting to a pre 3.1.0
(i.e. 3.0.9 and earlier, protocol version 30) server running in daemon
mode and requesting
a recursive (incremental by default) file transfer, the variable
use_safe_inc_flist is not set (affecting how I/O errors are handled
during file list generation).
so it is set for:
3.0.9 client -> 3.0.9 daemon
3.0.9 client ->
2016 Jan 08
0
LGPL relicense port of rsync
Am 07.01.2016 um 23:26 schrieb Per Lundqvist:
> Hi,
>
> I am maintaining a port of rsync (https://github.com/perlundq/yajsync)
> which is GPL:ed of course. The main purpose of the project is to
> provide a Java API library for the rsync protocol. It would
> therefore be really nice to be able to use LGPL as the license.
>
> But in order to do so I would first have to get a list of all the
> indiv...
2016 Jan 23
0
LGPL relicense port of rsync
Hi,
from my point of view:
On Sat, 9 Jan 2016 14:48:09 +0100
Per Lundqvist <perlundq at gmail.com> wrote:
> ...
> > Getting the approval for a relicensing I think the contributions to
> > rsync have to be analyzed in detail to approach a reasonable number of
> > contributors.
> >
> > I experienced that finding a responsible person that is willin...
2016 Jan 09
3
LGPL relicense port of rsync
...
> Getting the approval for a relicensing I think the contributions to
> rsync have to be analyzed in detail to approach a reasonable number of
> contributors.
>
> I experienced that finding a responsible person that is willing to
> discuss such a case in an organization that contributed source code is
> nearly impossible.
>
> Looking at the source code (my short
2016 Jan 24
0
LGPL relicense port of rsync
Hi Martin,
2016-01-23 18:41 GMT+01:00 Martin Pool <mbp at sourcefrog.net>:
> It seems like yajsync is a reimplementation of rsync's protocol by looking
> at the GPL'd C rsync source, but it doesn't actually include any code from
> rsync. Is that right?
Yes correct, it is a complete rewrite in Java. Most of it is
completely different, only some small parts of the actual
2016 Jan 24
2
LGPL relicense port of rsync
Hi Andrey,
2016-01-23 4:02 GMT+01:00 Andrey Gursky <andrey.gursky at e-mail.ua>:
...
> If they don't want to bother with just discussing, why would they take a
> big effort to claim? And your proposition for LGPL is not very
> different in opposite to BSD or public domain.
Yes, I agree. The risk of having a future lawsuit against my project
would be pretty small if I