Re: krusader - directory/file sync bug
Shie Erlich
Dear Shie,
first I have to say I really like Krusader - it generally helps to get things
done quickly.
One issue remained over the years - timestamps of files when using the
synchronisation tool.
When I synchronise two directories - say my linux box with a mac over sftp.
There is an inconsistent behaviour.
Files coming from the mac to my local machine (linux) - keep the date/time of
the original file. But files synchronised from the linux box to the mac will
change time/date to the point in time when it's been copied.
When I sync again - I end up with the file being copied on to the linux box
with the "new" date/time (the time I synced it on to the mac).
This behaviour makes the whole sync unusable.
Any Idea why it is doing that and what to do about it?
cheers,
Denny
Jan Lepper
Hi Shie, thanks for forwarding this.
@Denny: could you please report this at bugs.kde.org ?
@All: looks like another show-stopper for 2.4.
I'm seriously considering disabling certain features/modules by default for
the release.
The release announcement would then include a notice, that these features, due
to the lack of developers currently lack maintenance, and how to enable them
(at ones own risk).
Bye,
Jan
Yuri Chornoivan
Hi,
Should this notice (and the warning to the sections for every disabled
module) be put in the documentation?
If so, can you compile the list if the disabled functions for me to
put the warnings in the documentation and give KDE translation teams
time to translate them properly?
Thanks in advance for your answers.
Best regards,
Yuri
Jan Lepper
-------- Original-Nachricht --------
> Datum: Fri, 20 Jan 2012 11:34:14 +0200
> Von: Yuri Chornoivan <yur...@gmail.com>
> An: krusade...@googlegroups.com
> Betreff: Re: [Krusader-devel] Re: krusader - directory/file sync bug
Hi Yuri,
> Hi,
>
> Should this notice (and the warning to the sections for every disabled
> module) be put in the documentation?
>
I guess that would be helpful although it breaks the string freeze.
(Or doesn't it ? I'm not sure about the documentation.)
> If so, can you compile the list if the disabled functions for me to
> put the warnings in the documentation and give KDE translation teams
> time to translate them properly?
>
I will do so, once I have figured out which will be disabled.
> Thanks in advance for your answers.
>
> Best regards,
> Yuri
>
> --
> You received this message because you are subscribed to the Google Groups
> "krusader-devel" group.
> To post to this group, send email to krusade...@googlegroups.com.
> To unsubscribe from this group, send email to
> krusader-deve...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/krusader-devel?hl=en.
>
bye,
Jan
--
NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!
Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
Yuri Chornoivan
Hi Jan,
> Hi Yuri,
>
>> Hi,
>>
>> Should this notice (and the warning to the sections for every disabled
>> module) be put in the documentation?
>>
>
> I guess that would be helpful although it breaks the string freeze.
> (Or doesn't it ? I'm not sure about the documentation.)
It does not. If the proper documentation parts will be commented or
some minor note will be added it does not break freeze much.
Anyway, I can ask for translators approval in kde-i18n-doc and you
always have my Ok (as one of the translators). ;)
>> If so, can you compile the list if the disabled functions for me to
>> put the warnings in the documentation and give KDE translation teams
>> time to translate them properly?
>>
>
> I will do so, once I have figured out which will be disabled.
Thank you.
Best regards,
Yuri
jan
I won't bother disabling anything, it should be enough to mention
unmaintained modules in the release note.
Additionally a warning could be displayed once on startup.
Jan