On Sat, Sep 11, 2004 at 12:00:54PM +0200, Dirk Pape wrote:
> will my feature request be considered for one of the next rsync releases?
I'm not currently convinced that this is a big enough deal for most
people to warrant an option for the mainstream release, especially if we
have to ship a mergeso
Hello,
--Am Mittwoch, 25. August 2004 8:44 Uhr +0200 schrieb Dirk Pape
<[EMAIL PROTECTED]>:
Since in our scenario using rsync we rely on deterministic behaviour, we
patched rsync to use mergesort always for composing the file list. For
systems without a mergesort system call (most os's except fre
Hello Paul,
--Am Mittwoch, 25. August 2004 16:59 Uhr +0200 schrieb Paul Slootman
<[EMAIL PROTECTED]>:
In the meantime I'm curious about the relative memory usage of qsort
vs. mergesort. I'd hate rsync's memory usage to go up again.
as far as I am informed (I am not a profi in complexity)
mergeso
Hello Paul,
--Am Mittwoch, 25. August 2004 16:59 Uhr +0200 schrieb Paul Slootman
<[EMAIL PROTECTED]>:
Ah, so you were also lying when you said that the same file existed at
more than one source; the fileNAME is the same, but the file itself is
different.
I would prefer to say that I was mistaking
Hello Wayne,
--Am Mittwoch, 25. August 2004 9:03 Uhr -0700 schrieb Wayne Davison
<[EMAIL PROTECTED]>:
What would you think of a tie-break for identical names that depended on
some other attribute of the files? Such as newest file wins? That
would be quite easy to add and would be deterministic,
On Wed, Aug 25, 2004 at 08:44:15AM +0200, Dirk Pape wrote:
> Since in our scenario using rsync we rely on deterministic behaviour
What would you think of a tie-break for identical names that depended on
some other attribute of the files? Such as newest file wins? That
would be quite easy to add
On Wed 25 Aug 2004, Dirk Pape wrote:
> --Am Mittwoch, 25. August 2004 10:03 Uhr +0200 schrieb Paul Slootman
> <[EMAIL PROTECTED]>:
>
> >What I'm wondering is why it's a problem that the same file is
> >"randomly" copied from one of a number of sources, if indeed it is the
> >same file. The result
Hallo Paul,
--Am Mittwoch, 25. August 2004 10:03 Uhr +0200 schrieb Paul Slootman
<[EMAIL PROTECTED]>:
What I'm wondering is why it's a problem that the same file is
"randomly" copied from one of a number of sources, if indeed it is the
same file. The resulting destination will be the same, right?
On Wed 25 Aug 2004, Dirk Pape wrote:
> some time ago I reported a bug, where we saw indeterministic behaviour of
> rsync (all versions since 2.5), when having the same file appearing in
> multiple sources. Sometimes the file in the first source was copied, other
> times the file was copied from
Hello,
some time ago I reported a bug, where we saw indeterministic behaviour of
rsync (all versions since 2.5), when having the same file appearing in
multiple sources. Sometimes the file in the first source was copied, other
times the file was copied from one of the other sources.
The attache
10 matches
Mail list logo
